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

With no annotations, the description carries the full behavioral burden and delivers none of it: no indication of whether routing is a read-only lookup or triggers execution/side effects, no auth or payment requirements, no behavior on ambiguous or unsupported tasks. 'Route a task' is the entire behavioral disclosure.

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?

It is a single short, front-loaded sentence with no padding, so it is structurally clean. However, the brevity is under-specification rather than efficiency — the sentence is too thin for a 3-parameter routing tool.

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 three undocumented parameters, no annotations, and no output schema, the description supplies none of the missing context: not the routing taxonomy, not the input format, not the return shape. It is inadequate for the tool's complexity.

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?

Three parameters (task, input, query) at 0% schema description coverage, and the description explains none of them. The overlap between 'input' and 'query' is especially confusing and unaddressed; an agent cannot know which to populate or whether task is a natural-language instruction or an enum-like selector.

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 restates the name: 'Task Router: Route a task to the right service' adds no verb+resource specificity beyond the title. It doesn't say what 'routing' means — model dispatch, service selection, URL resolution — and gives no differentiation from the hundreds of x402 siblings (e.g. service_discovery, x402-search) that could plausibly do the same job.

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?

No when-to-use, when-not-to-use, or alternative is mentioned, despite obvious competing tools like service_discovery and get_stats in the sibling list. An agent has no basis to choose this router over searching the catalog directly.

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