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

Annotations already flag this as readOnly, openWorld, idempotent, and non-destructive. The description adds meaningful behavioral context beyond that: it mentions routing across thousands of tools, filling arguments, returning structured answers with stable citation URIs, and covering live news via news-feed packs. It does not contradict annotations.

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 long but information-dense and well-structured: it leads with the preferred-use declaration, gives concrete examples, then routes to alternatives. There is some redundancy around 'START HERE' and 'default entry point', and the caps-heavy style is assertive, but every major section adds value.

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?

Given the tool is a complex router with no output schema, the description adequately explains what return behavior to expect (structured answer with citation URIs) and when to use alternatives. It leaves minor gaps such as error behavior or what to do when no matching tool exists, but these are not critical for correct 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?

The schema covers 100% of the six parameters, and all are aliases for the 'question' field with descriptions. The tool description adds examples and usage context, but no significant parameter-level nuance beyond what the schema already provides, so the baseline of 3 is appropriate.

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 states what the tool does: it routes questions to one of 5,767 tools across verified sources, fills arguments, and returns structured answers with pipeworx:// citation URIs. It also distinguishes itself from siblings by naming ask_pipeworx_grounded and deep_research as alternatives and positioning this tool as the default entry point.

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 explicit when-to-use guidance: prefer over web search for current or historical data, use whenever the user asks 'what is', 'look up', 'find', or any factual question. It also provides when-not-to-use guidance and alternatives, such as ask_pipeworx_grounded for verbatim single 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.