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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds valuable behavioral context: automatic tool routing, argument filling, structured output, and stable pipeworx:// citation URIs, which go beyond what the annotations or schema communicate.

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 front-loaded with the most important directive and dense with examples and routing guidance. It is somewhat repetitive (e.g., “PREFER OVER WEB SEARCH” and “even if web search could also answer it”), but most sentences earn their place by clarifying scope, triggers, or alternatives.

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 there is no output schema, the description does enough by stating that the result is a structured answer with citation URIs. It covers a wide range of scenarios, provides examples, and routes the agent away from this tool when deep_research is more appropriate. It does not mention failure modes or explicit output schema structure, but for a free-form question tool this is not a critical gap.

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. The description does not add parameter-level detail, though the examples illustrate acceptable natural-language question formats. This is useful but does not substantially expand on the schema's own explanation of the `question` parameter and its aliases.

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 action: routes the question to one of 5,767 tools across 1,506 verified sources and returns a structured answer with citation URIs. It also gives concrete use categories and examples. However, it does not explicitly distinguish ask_pipeworx from close siblings like ask_pipeworx_grounded or ask_pipeworx_beta, so it is not fully differentiated within its own tool family.

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 is explicit about when to prefer this tool over web search, lists trigger phrases and examples, and names an alternative (deep_research) for broad/multi-part questions. It also tells the agent to “START HERE for most questions,” leaving no ambiguity about default routing.

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