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

Annotations already convey read-only, open-world, and idempotent behavior. The description adds beyond that: it fills arguments, routes across thousands of tools, returns stable citation URIs, works on every tier, and is one fast call. This gives practical behavioral context without contradicting the annotations.

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 longer than minimal but every major block serves a purpose: preference over web search, routing mechanism, usage triggers, examples, and escalation paths. It is front-loaded with the most important guidance, though the repeated emphasis and lengthy example list prevent a 5.

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?

Even without an output schema, the description tells the agent what to expect: a structured answer with pipeworx:// citation URIs. It also covers when to use this tool, when to use alternatives, and what types of questions are appropriate. Nothing critical for invoking it correctly is missing.

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 described in the input schema with 100% coverage, so the schema does the heavy lifting. The description adds no parameter-specific semantics beyond natural-language example questions. Per the baseline rule for full schema coverage, a 3 is appropriate.

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 names a specific verb and resource: it 'Routes the question to the right one of 5,743 tools across 1500 verified sources' and returns structured answers with pipeworx:// citation URIs. It also marks itself as the default entry point, distinguishing it from siblings like ask_pipeworx_grounded and deep_research.

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 lists trigger phrases like 'what is', 'look up', 'get the latest'. It also names alternatives and the exact conditions to step up: ask_pipeworx_grounded for hallucination-resistant single answers and deep_research for broad multi-part questions.

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