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

Annotations already establish readOnlyHint, openWorldHint, idempotentHint, and non-destructiveness. The description adds meaningful behavioral context beyond that: it routes to a large corpus, fills arguments automatically, and returns structured answers with pipeworx:// citation URIs. It also notes speed and tier availability, so the agent knows what to expect from the call.

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: it front-loads the core preference over web search, then lists supported domains, triggering phrases, examples, and escalation paths. Some redundancy exists between the domain list and the examples, but every section serves a distinct routing purpose. It earns a 4 rather than 5 because it could be tightened without losing value.

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 question-answering tool with no output schema, the description covers all essential ground: supported domains, when to use it, alternatives, examples, return format, and citation behavior. It explicitly states the output includes structured answers with stable citation URIs, which compensates for the missing output schema. An agent has enough information to invoke and interpret the result 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?

Schema description coverage is 100%, and the description adds no parameter-specific details beyond the schema. The schema already documents 'question' and all aliases clearly, with examples, so the description does not need to compensate. The baseline 3 is appropriate because the tool relies on the schema for parameter semantics.

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 specific function: routing questions to 5,721 tools across 1,497 verified sources and returning structured answers with stable citation URIs. It clearly distinguishes itself from siblings like ask_pipeworx_grounded and deep_research, and positions itself as the default entry point. This leaves no ambiguity about what the tool does.

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 explicitly tells the agent to prefer this tool over web search for factual questions, and gives concrete query patterns like 'what is', 'look up', 'find', and 'get the latest'. It also names alternatives for specific cases: ask_pipeworx_grounded for hallucination-resistant single answers and deep_research for broad/multi-part questions. This is exemplary when-to-use guidance.

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