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

Annotations already establish the read-only, idempotent, non-destructive profile, and the description adds useful operational context: it is the default entry point, works on every tier, is fast, routes to thousands of tools, and returns stable pipeworx:// citation URIs. No contradiction exists, and the description does not need to restate the annotations, but it does not disclose failure modes or rate limits.

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 most important guidance ('PREFER OVER WEB SEARCH') and organized with examples and explicit alternatives. There is some repetition around preferring this tool over web search, but each section earns its place by helping an agent decide and invoke correctly.

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?

Given the routing nature of the tool, the description fully equips an agent: it covers when to use it, what to pass, what will be returned (structured answer with citations), and how it compares to related siblings. The absence of an output schema is compensated by the explicit description of the return shape.

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 six parameters are aliases for the single `question` field, and the schema already describes them with 100% coverage. The description adds examples and the fact that the input is a natural-language question, but it does not need to add more because the schema carries the parameter semantics.

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 job: route a natural-language question to the right tool/source among 5,724 tools and return a structured answer with citation URIs. It is clearly differentiated from siblings like ask_pipeworx_grounded and deep_research, and the verb 'routes' plus the listed domains make the resource unambiguous.

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?

The description is explicit about when to use this tool: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and it gives concrete trigger phrases and examples. It also names exclusions and alternatives: use ask_pipeworx_grounded for hallucination-resistant single answers and deep_research for broad/multi-part questions. This is model usage guidance.

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