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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: it routes to one of 5,743 tools, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. This explains how the tool behaves rather than merely what it is called.

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 'PREFER OVER WEB SEARCH' directive and gives useful categories and examples. However, it becomes redundant by repeating 'even if web search could also answer it' and then ends with a confusing, garbled suffix about 'what's the world saying about X' and '*-news-feeds packs' that undercuts clarity. Some sentences could be trimmed or removed.

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 no output schema, the description explains the return shape: a structured answer with stable pipeworx:// citation URIs. It covers supported domains, trigger phrasing, and example queries. It is reasonably complete for a broad routing tool, though it does not address edge cases or explicitly clarify the relationship to the beta/grounded siblings.

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 all six parameters documented as aliases for the question field. The description adds practical examples and query phrasing guidance, but it does not add parameter-level semantics beyond what the schema already provides. Baseline 3 is appropriate because the schema carries the parameter documentation burden.

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 ask_pipeworx as a general factual-question routing tool that handles structured, authoritative data and returns cited answers. It includes concrete categories and examples. However, it does not explicitly differentiate itself from the sibling tools ask_pipeworx_beta and ask_pipeworx_grounded, so it falls short of full sibling differentiation.

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 strong when-to-use signals: prefer over web search for factual questions, start here for most questions, and use even when web search could answer. It also exemplifies trigger phrases like 'what is', 'look up', and 'current'. It does not provide exclusions or mention when a sibling like deep_research or ask_pipeworx_grounded would be more appropriate, so there is a clear context but no alternative routing guidance.

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