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

The annotations provide readOnly/openWorld/idempotent hints, but the description adds meaningful behavioral context: it routes to one of 5,743 tools, fills arguments internally, and returns a structured answer with stable pipeworx:// citation URIs. This goes beyond the annotations and helps the agent predict what invoking the tool will do. 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 opening is dense and valuable, but the description becomes repetitive: the example list and the 'START HERE for most questions' sentence appear twice, padding length without adding new information. It front-loads the most important guidance but does not earn every sentence it contains.

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 that takes a single free-text question and has no output schema, the description supplies the needed use context, input expectation, and output shape: structured answer with citations. It could mention limitations or which sibling tools it should be preferred over, but it is substantially complete for an agent 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%, and all six schema properties are aliases for the same natural-language question. The schema already documents the parameter meaning well. The tool description adds example queries but no additional parameter-level semantics, so the baseline score of 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 the tool as a question-routing/fact-answer tool: it 'routes the question to the right one of 5,743 tools' and returns structured answers with citations. It is explicit about the domain (current or historical data, authoritative sources). It does not, however, differentiate from sibling tools like 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 strong when-to-use signals: 'PREFER OVER WEB SEARCH', 'Use whenever the user asks...', 'START HERE for most questions', and multiple concrete example queries. It lacks explicit when-not-to-use exclusions or direction to an alternative sibling tool, so it is clear but not fully exhaustive.

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