Ac Agent Tool Design

Deciding what tools an agent gets and shaping each one so the model uses it correctly: which capabilities deserve to be tools at all, writing descriptions the model actually reads, result payloads sized for a context window, the tool menu and its confusion costs, error returns that teach recovery instead of dead ends, and the written tool-surface record. It teaches the craft of the tool interface seen from the model's side; it never recommends a framework and never promises an agent will behave. Use when asking "should this be a tool", "tool description writing", "how many tools is too many", "tool naming", "tool result format", "tool menu design", "agent tool design", "tool error messages", "tool schema design", "when not to give an agent a tool". Not for the client-side agent loop and multi-turn plumbing (ac-llm-api-integration), not for MCP server protocol and transport (ac-mcp-authoring), not for sandboxing what a tool may touch (ac-wasm-and-sandboxes).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit 408f60457e

Frequently asked questions

npx get-skill add jiayaoqijia/ac-agent-tool-design