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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses how the tool behaves internally: it routes to one of thousands of tools, fills arguments, returns structured answers with stable pipeworx:// citation URIs, and works on every tier. This adds meaningful context, though it does not cover failure modes or rate limits.

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 every sentence earns its place: primary use case, tool mechanics, trigger phrases, examples, default entry point, and upgrade paths to siblings are all front-loaded and purposeful. It is slightly verbose but well-structured for agent decision-making.

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 single-required-parameter tool with no output schema, the description is thorough: it covers when to use it, how it routes queries, what kind of answer to expect, and how it compares to sibling tools. Nothing essential for correct invocation 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?

The schema already documents all six parameters as aliases for the natural-language question field (100% coverage), so the description is not required to add much. It does not deepen parameter-level understanding beyond what the schema provides, but it does give examples of acceptable queries in context.

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 specific verb and resource: it routes a natural-language question to the right one of 5,724 tools across 1,497 verified sources and returns structured answers. It explicitly distinguishes itself from sibling tools like ask_pipeworx_grounded and deep_research by describing what makes each different.

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 highly explicit usage guidance: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and 'Step up only when needed' with named alternatives. It also provides trigger phrases and examples, and clarifies when ask_pipeworx already covers cases like breaking news.

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