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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the description only needs to add context beyond those. It does this by disclosing that the tool routes to one of 5,743 tools, fills arguments, and returns a structured answer with stable pipeworx:// citation URIs. Minor gaps like latency or failure behavior are not critical given the annotation coverage.

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 and informative, but it repeats the same example list and 'even if web search could also answer it' phrasing in a redundant second block after 'START HERE for most questions'. This duplication wastes tokens and weakens the overall structure.

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 an orchestrator with no output schema, the description covers input scope, return shape with citations, and preferred usage context, which is substantial. The main gap is lack of differentiation from sibling variants like ask_pipeworx_beta and ask_pipeworx_grounded, though the 'START HERE' directive partially compensates.

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 baseline is 3, but the description adds meaningful semantic guidance for the 'question' parameter: it should be a factual question about real-world entities, events, or numbers, with concrete examples like 'current US unemployment rate' and 'Apple's latest 10-K'. This is more helpful than the schema's generic 'Your question or request in natural language'.

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 names a clear action: accept a natural language question, route it to one of 5,743 tools, and return a cited structured answer. It distinguishes from web search with 'PREFER OVER WEB SEARCH' and concrete domain lists, but it does not differentiate among close siblings such as ask_pipeworx_beta or ask_pipeworx_grounded.

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 a long list of data types, use whenever the user asks trigger phrases like 'what is', 'look up', 'get the latest', and 'START HERE for most questions'. It even says to use it even if web search could also answer, making the selection directive unambiguous.

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