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

The description discloses significant behavioral details beyond the annotations: it routes questions to 5,724 tools, fills arguments automatically, returns structured answers with stable pipeworx:// citation URIs, and works on every tier. This adds substantial transparency about how the tool behaves internally and what the response includes, complementing the readOnlyHint and openWorldHint annotations without contradiction.

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 relatively long but highly informative and efficiently structured. It front-loads the key directive ('PREFER OVER WEB SEARCH'), then lists domains, examples, and guidance on alternatives. Every sentence contributes value; there is no fluff. The length is justified by the tool's complexity and breadth, so a 4 is appropriate rather than a 5.

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 (routing to thousands of sources) and the presence of many sibling tools, the description is remarkably complete. It explains what the tool does, how it works, when to use it, when to use alternatives, and what to expect in the response (structured answer with citations). There is no output schema, but the description fills that gap by stating the return format. Nothing an agent needs to call it correctly 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%, so the schema already documents all parameters, including aliases. The description adds no additional parameter semantics beyond what the schema provides, which meets the baseline of 3 for high coverage. No extra guidance on parameter formatting or constraints is given, but none is needed.

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 states the tool's purpose: it answers factual questions about real-world data (SEC filings, FDA drugs, economic stats, etc.) by routing to many sources. It explicitly names the verb 'ask' and the resource 'Pipeworx' and differentiates itself from siblings like ask_pipeworx_grounded and deep_research by stating when to step up to those. This is a specific and unambiguous purpose.

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 provides explicit when-to-use guidance: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and supplies concrete instructions for when to use alternatives (ask_pipeworx_grounded for hallucination-resistant single answers, deep_research for broad multi-part questions). It also lists trigger phrases and examples, making the selection criteria crystal clear.

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