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

Beyond the readOnly/openWorld/idempotent annotations, the description reveals important behavior: it auto-routes the question, fills tool arguments, returns structured answers with stable pipeworx:// citation URIs, works on every tier, and makes a single fast call. This gives the agent an accurate mental model of what happens when the tool is invoked.

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: it front-loads the most critical routing advice, gives concrete examples, clarifies the default status, and names the alternatives with conditions. It is well-structured and information-dense without being redundant.

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?

Despite having no output schema, the description compensates by explaining what the output looks like: a structured answer with stable citation URIs. It also covers input expectations, scope, fallback tools, and tier availability, so an agent has enough context to invoke the 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?

Schema coverage is 100%, and the schema already documents the question parameter plus all aliases. The description adds useful examples of natural-language questions, but it does not need to explain parameter semantics further because the input schema fully carries that 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 defines ask_pipeworx as the default entry point for factual and real-world data questions, explaining that it routes to thousands of tools and returns structured answers with citation URIs. It also explicitly differentiates it from ask_pipeworx_grounded and deep_research, giving the tool a unique and unmistakable role.

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, including 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and common query patterns. It also gives when-not-to-use conditions by directing hallucination-sensitive asks to ask_pipeworx_grounded and broad multi-part research to deep_research, making the routing decision clear.

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