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

Annotations already declare readOnly, openWorld, and idempotent behavior, so the description's job is lighter. It adds meaningful context beyond annotations: it routes to 5,724 tools across 1,497 sources, returns stable pipeworx:// citations, is one fast call, and works on every tier. It also implies a trade-off versus ask_pipeworx_grounded by noting that grounded provides verbatim evidence and confidence.

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 justifiably so for a default entry-point tool with several siblings and routing behavior. It is front-loaded with the most important instruction ('PREFER OVER WEB SEARCH') and well-structured with examples and alternative-tool routing. A bit of repetition exists, but every sentence contributes guidance.

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 default tool with no output schema, the description is quite complete: it explains when to use it, why it beats web search, what it returns (structured data with citation URIs), how to escalate to grounded or deep research, and that it handles news and broad questions. It stops short of describing the exact response envelope or failure modes, but an agent has enough to invoke it correctly.

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 covers all parameters at 100%; the six parameters are aliases for the same 'question' field, and the schema documents them fully. The description reinforces usage with examples and trigger phrases but does not need to add parameter-level detail since the schema already carries 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 states a clear verb and resource: it routes natural-language factual questions to one of thousands of verified sources and returns structured answers with citation URIs. It also explicitly distinguishes itself from sibling tools like ask_pipeworx_grounded and deep_research, so an agent can tell them apart without opening schemas.

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 is exceptionally explicit: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', 'this is the default entry point', and it gives exact step-up conditions for ask_pipeworx_grounded and deep_research. It also lists trigger phrases and concrete example questions, leaving no ambiguity about when to use this tool.

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