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

Annotations already mark it read-only, idempotent, and open-world, so the safety profile is covered. The description adds meaningful behavioral context beyond the annotations: it routes to internal sources, fills arguments automatically, returns structured output with stable pipeworx:// citation URIs, works on every tier, and is a single fast call. There is no contradiction with 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 long but every sentence earns its place: usage priority, scope, examples, alternatives, and escalation path are all packed in without redundancy. The most important directive ('PREFER OVER WEB SEARCH') is front-loaded, and the examples concretely illustrate the expected input style.

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 central routing tool with no output schema, the description is complete: it states what the tool does, when to use it, how it behaves, what it returns, and how it compares to siblings. An agent has enough context to select and invoke ask_pipeworx correctly without hunting for more information.

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%, so the schema already documents the single meaningful parameter and its aliases. The description reinforces that the input is a natural-language question but adds no additional parameter-level semantics beyond what the schema provides. This matches the baseline for high schema coverage.

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 questions to one of 5,743 tools across 1,500 sources and returns structured answers with citation URIs. It sharply distinguishes itself from ask_pipeworx_grounded and deep_research by naming them as alternatives. This is far beyond a vague or tautological statement.

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 gives explicit when-to-use guidance: prefer over web search, use for factual/real-world questions, and start here as the default entry point. It also explains when to step up to ask_pipeworx_grounded or deep_research, providing concrete conditions and examples. No ambiguity remains about when this tool is appropriate.

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