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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds useful context beyond that: this tool routes to 5,798 tools across 1,517 verified sources, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. This clarifies the orchestration behavior and output nature without contradicting the 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 description is longer than average but almost every part earns its place: target domains, trigger phrases, examples, and an explicit alternative. Critical guidance is front-loaded with "PREFER OVER WEB SEARCH" and "START HERE for most questions." It could be tightened slightly, but it is structurally effective.

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, the description is remarkably complete: it explains what it does, when to use it, when not to use it, provides representative examples, and describes the output as a structured answer with citation URIs. Even without an output schema, an agent has enough context to invoke this tool correctly and interpret the result.

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?

The input schema has 100% description coverage: all six parameters are documented as aliases for a single natural-language question, with examples. The description adds little beyond that, so it is correct to give the schema the credit. The baseline of 3 applies because the schema fully carries the parameter documentation burden.

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: route factual questions to a large set of authoritative data sources and return a structured answer with citations. It provides many concrete domains and examples. However, it does not explicitly differentiate ask_pipeworx from sibling variants like ask_pipeworx_beta or ask_pipeworx_grounded, so it is clear but not fully sibling-distinguishing.

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 guidance: prefer this over web search, use it for factual questions even when web search could answer, and start here for most questions. It also names a concrete alternative, deep_research, for broad/multi-part questions, which is exactly the kind of when-to-use vs. when-not-to-use guidance an agent needs.

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