Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses LLM credit costs, three routing outcomes (persisted Ask Clarity, spawned Aurora research, queued single-tool fulfill), and adaptive routing. It omits auth and response/async details, but the behavioral context is substantial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The cost warning is front-loaded, and the four sentences each add distinct value: cost/path, routing behavior, usage guidance, and adaptive selection. There is no filler or redundancy that hurts clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations and no output schema, the description gives strong context about behavior, cost, and route selection, while the schema covers all parameters. It does not explain return values or async completion, which is a minor gap given the tool can queue jobs or spawn agents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds no per-parameter meaning beyond what the schema provides, but it does not need to because the schema entries are adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool sends a chat message via the POST /api/chat path and orients it as the tool 'for chat turns'. It explicitly contrasts with create_agent, but it does not address send_agent_message, so sibling differentiation is partial rather than complete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit selection guidance: 'Use this for chat turns; use create_agent only when you explicitly want agent spawn without single-tool fulfill.' This directly tells the agent when to choose this tool versus the main ambiguous sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.