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

Annotations already cover the safety profile (read-only, idempotent, open-world). The description adds meaningful behavioral context: it routes internally, fills arguments automatically, and returns structured answers with stable citation URIs. It doesn't discuss failure modes or limits, but given annotation coverage, this is a solid disclosure.

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 front-loaded with the most important guidance and includes a dense but helpful list of domains, trigger phrases, and examples. It loses a point for minor run-on/formatting issues in the 'step up' section and for being slightly longer than necessary, but every sentence earns its place.

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 broad meta-tool with no output schema, the description covers routing behavior, citation guarantees, domain scope, example queries, and escalation paths to sibling tools. It doesn't specify the exact response shape, but the schema and examples provide enough for an agent to select and invoke the tool correctly.

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% with clear alias descriptions for all six parameters, so the description doesn't need to add parameter-level semantics. It does provide useful example phrasings for the question parameter, but that is marginal additional value beyond the schema's examples and descriptions.

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 clearly identifies the tool as a natural-language entry point that routes questions to one of 5,798 tools across 1,517 verified sources and returns structured answers with pipeworx:// citation URIs. It also explicitly frames itself as the preferred alternative to web search, which distinguishes it from sibling tools 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?

It gives explicit when-to-use instructions ('PREFER OVER WEB SEARCH', 'START HERE for most questions', 'Use whenever the user asks...'), provides concrete trigger phrases and example queries, and names the conditions for escalating to ask_pipeworx_grounded or deep_research. This is strong routing guidance with specific alternatives.

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