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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral detail beyond those: it routes to one of 5,908 tools, fills arguments, and returns structured answers with stable pipeworx:// citation URIs. No contradiction with 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 front-loaded with the key directive 'PREFER OVER WEB SEARCH' and is organized into usage instructions, trigger phrases, examples, and a closing recommendation. It is longer than strictly minimal, but each section contributes actionable guidance rather than filler.

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?

There is no output schema, so the description carries the burden of explaining what the agent receives; it does so by mentioning structured answers and stable citation URIs. It also covers a wide range of factual question types. It could be more complete by addressing when not to use this tool or how it differs from sibling variants, but overall it is sufficient for an open-ended router 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%, so the parameter list is well documented. The description adds value by clarifying the expected input shape: natural-language factual questions, with examples like 'current US unemployment rate' and 'Apple's latest 10-K'. This helps an agent form better queries without being strictly necessary given the schema.

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 a specific verb and resource: ask a natural-language factual question and receive authoritative structured data with citations. It also explicitly distinguishes itself from web search. However, it does not differentiate itself from the sibling tools ask_pipeworx_beta and ask_pipeworx_grounded, so purpose clarity is strong but not complete.

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 guidance: prefer this over web search for factual questions, lists trigger phrases such as 'what is', 'look up', 'get the latest', and says 'START HERE for most questions'. It does not state when to use the sibling ask_pipeworx variants instead, but the usage context is otherwise clear and practical.

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