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

Beyond the read-only/idempotent annotations, the description discloses substantive behavior: the tool routes questions internally, fills arguments, returns structured answers with stable pipeworx:// citation URIs, works on every tier, and requires one fast call. It even clarifies that it can answer questions web search could also answer. No contradiction with annotations.

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 organized: priority directive, scope, examples, escalation path, and news caveat. Each section earns its place for such a broad default tool. It loses one point because 'PREFER OVER WEB SEARCH', 'Use whenever', and 'START HERE' overlap in message, adding mild redundancy.

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?

There is no output schema, so the description correctly carries the return-value context: structured answer with citation URIs. It also covers tool scope, example queries, alternatives, tier availability, speed, and news handling. This is as complete as an entry-point dispatcher needs to be.

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%, so the baseline is 3, but the description still adds value by emphasizing that a single natural-language question is the meaningful input and that the tool fills arguments. It also provides concrete example questions showing the expected phrasing. It correctly avoids duplicating the alias list already present in the schema.

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 names a specific behavior ('routes the question') and a concrete resource: 5,743 tools across 1,500 verified sources. It also separates this tool from siblings by naming ask_pipeworx_grounded and deep_research as different options. The 'PREFER OVER WEB SEARCH' framing makes its purpose unmistakable.

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?

It explicitly states when to use this tool: for factual questions about real-world entities, including phrases like 'what is', 'look up', 'find', and 'get the latest'. It also provides escalation paths to ask_pipeworx_grounded and deep_research, and notes how breaking-news queries are handled. This is explicit when/when-not guidance, not just implied context.

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