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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it explains that Pipeworx routes to the right tool, fills arguments, and returns structured answers with stable pipeworx:// citation URIs. That tells the agent about the response format and citation behavior without conflicting with any annotation.

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?

Extremely information-dense and front-loaded, but the second half of the description becomes a run-on with awkward stitching ('when needed: for a broad/multi-part question...'), and there is some redundancy with repeated examples and routing guidance. Valuable content, but structurally it degrades into a wall of text rather than clean, scannable guidance.

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 1-required-parameter, auto-routing tool with no output schema, the description supplies everything needed: when to use it, what domains it covers, what to expect back (structured answers, citations), and how to decide among close siblings. The alias list in the parameter schema completes the picture for invocation.

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 fully documents the aliases and the main 'question' parameter. The description reinforces that the parameter is a natural-language question and lists example queries, but it doesn't add substantive new parameter semantics beyond what the schema already states. Baseline 3 is appropriate when the schema carries the full load.

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 is unusually explicit: a single verb ('ask Pipeworx routes the question'), a precise resource ('5,798 tools across 1517 verified sources'), and a clear differentiation from web search and sibling tools like deep_research and ask_pipeworx_grounded. It enumerates concrete domains (SEC, FDA, FRED/BLS, patents, real estate, weather, clinical trials, stocks, sports), making the tool's scope unmistakable.

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?

Provides explicit when-to-use ('PREFER OVER WEB SEARCH'), trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much'), concrete examples, and names sibling alternatives with the conditions that should route to them ('deep_research for broad/multi-part questions', 'ask_pipeworx_grounded for hallucination-resistant single answers'). This is exactly the kind of routing guidance an agent needs.

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