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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds valuable behavior beyond annotations: it routes to one of 5,743 tools, fills arguments, and returns stable pipeworx:// citation URIs, giving the agent a clearer mental model of execution.

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 lengthy but dense and well-structured: it front-loads the primary directive ('PREFER OVER WEB SEARCH'), then gives behavior, trigger phrases, examples, and sibling alternatives. There is some repetition around web-search comparison, but each section earns its place for a broad meta-tool.

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's complexity and the absence of an output schema, the description adequately covers what the tool returns ('structured answer with stable pipeworx:// citation URIs'), when to use it, what question formats to pass, and which siblings to choose for specialized needs. No critical invocation information is missing.

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%, with all six parameters documented as aliases for 'question'. The description adds useful examples and natural-language context, but it does not add meaningful parameter-level semantics beyond what the schema already says. Baseline 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 identifies a specific verb and resource: it routes a factual question to the right specialized tool and returns a structured answer with citations. It also distinguishes itself from siblings by explicitly naming ask_pipeworx_beta and ask_pipeworx_grounded as more specialized alternatives.

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 factual questions, provides trigger phrases like 'what is', 'look up', and 'get the latest', and includes concrete examples. It also states when not to use the main tool by pointing users to ask_pipeworx_beta and ask_pipeworx_grounded.

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