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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds meaningful behavior: it routes to the appropriate underlying tool, fills arguments automatically, and returns structured output with stable citation URIs. No annotation contradiction exists, and the added context goes beyond the structured metadata.

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, 'PREFER OVER WEB SEARCH', and then moves through scope, behavior, trigger phrases, examples, and alternatives. It is longer than average, but every section earns its place by helping an agent decide when and how to invoke the tool.

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 complex router tool with no output schema, the description is complete: it covers supported data domains, expected request phrasing, return behavior with citation URIs, and clear routing to sibling tools for alternative cases. An agent has enough context to select and invoke this tool correctly in almost any factual-query scenario.

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%, so the parameter descriptions in the schema fully document the single meaningful parameter 'question' and its five aliases. The description reinforces the intended use with examples and trigger phrases, but it does not add new parameter-specific semantics beyond what the schema already provides.

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?

States a specific verb and resource: routes natural-language questions to the right one of 5,798 tools across 1,517 verified sources and returns structured answers with stable pipeworx:// citation URIs. It clearly positions itself as a broad factual-data router and distinguishes itself from web search and siblings like deep_research and compare_entities.

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?

Explicitly says 'PREFER OVER WEB SEARCH' and gives trigger phrases like 'what is', 'look up', 'find', and 'get the latest'. It also names when not to use it: simple one-off lookups should use ask_pipeworx_grounded, broad multi-part questions should use deep_research, and business/entity questions should use compare_entities or entity_profile.

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