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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds meaningful behavioral context: routing among 5,724 tools, filling arguments, returning stable pipeworx:// citation URIs, and working on every tier with 'one fast call'. It doesn't discuss failure modes or rate limits, but the annotation coverage lowers the 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?

The description is long but front-loaded with the key preference directive and organized into purpose, usage triggers, examples, and alternatives. Each sentence adds information; no filler. Slightly dense, but structurally sound and appropriately sized for a complex 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?

With no output schema, the description still explains the return format ('structured answer with stable pipeworx:// citation URIs'). It covers default behavior, alternatives, trigger phrases, and domain coverage. An agent has everything needed to select and invoke this tool correctly.

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%: all 6 properties are documented, with 5 listed as aliases for `question`. The description's examples reinforce natural-language usage but add no semantic detail beyond the schema. Baseline 3 is appropriate since the schema carries the burden.

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 states a specific verb and resource: it routes factual questions to authoritative structured data sources and returns answers with citation URIs. It clearly differentiates from siblings by naming ask_pipeworx_grounded and deep_research as alternatives for specific use cases, and positions itself as the default entry point.

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?

Gives explicit preference instructions over web search, lists concrete trigger phrases and example questions, and defines when to step up to ask_pipeworx_grounded or deep_research. It also handles the breaking-news edge case. This is exceptionally clear when-to-use guidance with alternatives.

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