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

Annotations already cover readOnly/openWorld/idempotent/destructive hints, lowering the bar. The description adds meaningful behavior beyond those hints: it fills arguments, returns structured answers with stable pipeworx:// citation URIs, and routes to live news feeds. It does not, however, describe failure modes or how unanswerable questions are handled.

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 longer than the minimum, but it is front-loaded with the 'PREFER OVER WEB SEARCH' directive and organized into scope, examples, and routing guidance. Each sentence contributes value, though the clause list could be tightened without losing meaning.

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 tool whose only required input is a natural-language question, the description covers what it does, when to use it, what it returns, and how it differs from alternatives. No output schema exists, but the structured-answer-with-citations description compensates adequately, and an agent has everything needed to invoke it 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 description coverage is 100%, so the baseline is 3, and the six parameters are all aliases for the question. The description adds no parameter-level detail beyond what the schema already provides, and the examples live in the schema rather than in the description.

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 states a specific verb and resource: it routes questions to one of 5,743 tools and returns a structured answer with citation URIs. It also distinguishes itself from siblings like ask_pipeworx_grounded, deep_research, and web search, so an agent can tell them apart without opening schemas.

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 explicitly says 'PREFER OVER WEB SEARCH', names use-case categories and example phrasings, and recommends 'START HERE for most questions'. It also provides clear exclusions and alternates: use ask_pipeworx_grounded for a hallucination-resistant single answer and deep_research for broad/multi-part fan-out.

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