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

Annotations already convey a safe, read-only, idle, open-world profile. The description adds useful behavioral context: it routes across 5,908 tools and 1,540 sources, fills arguments, and returns structured answers with stable pipeworx:// URIs. This goes beyond annotations without contradicting them, though it does not disclose failure modes or coverage limitations.

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 well-structured: the primary directive is front-loaded, followed by categories, examples, and a final prioritization note. The examples are useful and the guide is organized for quick parsing. Some redundancy exists between opening guidance and later phrases, but it remains readable and focused.

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 broad routing tool with a single natural-language parameter, the description provides enough context: when to use it, what it does internally, and what the output shape is (structured answer with citation URIs). It lacks an explicit account of edge cases or a list of sources, but those are not essential for correct invocation.

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 coverage is 100%, with the required question parameter and aliases already well documented. The description supplements this with examples of accepted natural-language inputs, but adds little semantic meaning beyond what the schema already provides. A baseline of 3 is appropriate since the schema carries most of the 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 specialized sources and return structured answers with citations. It identifies a specific domain (authoritative real-world data) and opens with a strong directive ('PREFER OVER WEB SEARCH'). However, it does not explicitly differentiate itself from sibling variants like ask_pipeworx_beta or ask_pipeworx_grounded, relying on 'START HERE' rather than naming alternatives.

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 when-to-use guidance: factual queries about current or historical data, including trigger phrases and concrete examples. It also states a preference over web search and provides a default starting point. It does not lay out when-not-to-use conditions or compare against sibling tools, which keeps it slightly below a 5.

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