ck_route

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

States read-only behavior and no session state change. Lacks details on rate limits or authorization but is sufficient given the tool's nature. No annotations provided, so description carries full burden.

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?

Five sentences, all valuable. Front-loaded purpose, then details, then usage comparisons. No redundant information.

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?

Explains input parameters and return value (ranked list with rationale). Could mention output structure more explicitly, but given no output schema, it is largely sufficient.

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?

All 4 parameters have descriptions in the schema (100% coverage), and the description adds context: task is plain-language, risk_tier filters by security level, allowed_agents restricts subset. Defaults and omission behavior are clarified.

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's purpose: recommending the best AI agent based on security tier, budget, task type, and past performance. It distinguishes from siblings ck_delegate and ck_cost_optimizer by specifying when to use each.

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?

Explicit guidance is given: use ck_route to pick an agent, then ck_delegate to transfer; use ck_cost_optimizer for price-focused comparison. Default risk_tier and allowed_agents omission are noted.

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