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

Annotations cover read-only, open-world, idempotent, non-destructive behavior, and the description adds meaningful behavioral context: the tool auto-fills arguments, routes across thousands of tools, and returns stable pipeworx:// citation URIs. This makes the orchestrator behavior explicit rather than mysterious.

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?

Front-loaded with the most important guidance and data domains, with examples near the top. It earns its length, though it is slightly redundant: 'START HERE for most questions' restates the earlier use guidance, and the 'natural-language argument is filled in automatically' sentence repeats the earlier fills-arguments behavior.

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?

Despite having no output schema, the description tells the agent what to expect (structured answer with citation URIs) and how to invoke successfully. It also covers routing, alternatives, and input phrasing, so the agent has everything needed to select and call the tool.

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 coverage is 100% and already documents the question parameter plus aliases, so the baseline is 3. The description adds value by giving trigger phrases and six concrete example queries that clarify acceptable natural-language inputs.

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?

Description names a specific action: routes a natural-language question to one of 5,743 tools across verified sources, fills arguments, and returns a structured answer with citation URIs. It also differentiates from siblings by naming ask_pipeworx_grounded for grounded answers and deep_research for broad questions.

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?

Explicit when-to-use guidance is provided: prefer over web search for factual/current/historical data, with trigger phrases and concrete examples. It also states when to step up to alternatives, grounded for single hallucination-resistant 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.