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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds valuable operational behavior beyond annotations: it routes to sub-tools, fills arguments, returns structured answers with stable citation URIs, claims to work on every tier, and is a single fast call. This extra context helps an agent set expectations without contradicting any 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 longer than ideal and repeats the 'prefer over web search' / 'even if web search could also answer' idea, plus 'START HERE' and 'default entry point' are redundantly stated. However, it is well-structured, front-loaded with the most important instruction, and every major section (scope, examples, alternatives) earns its place. It earns a 4 because it is dense but not bloated.

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 no output schema, the description explains what the return looks like ('structured answer with stable pipeworx:// citation URIs'), enumerates covered domains, provides concrete examples, lists tier/performance characteristics, and explicitly names alternative tools for adjacent use cases. For a tool of this complexity, nothing critical is missing for correct selection and 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 description coverage is 100%, so parameter semantics are fully documented in the schema. The description adds natural-language examples that illustrate valid questions, but it does not introduce any new parameter-level meaning beyond the schema. Per the baseline, a score of 3 is appropriate when the schema carries the full weight.

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 uses strong, specific verbs: 'routes the question,' 'fills arguments,' 'returns the structured answer with stable pipeworx:// citation URIs.' It clearly identifies the resource (a meta-tool spanning 5,718 tools across 1,496 sources) and differentiates itself from siblings like ask_pipeworx_grounded and deep_research by naming them and their distinct purposes.

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 ('Use whenever the user asks...', 'START HERE for most questions') and when to step up to alternatives ('for a hallucination-resistant single answer... use ask_pipeworx_grounded; for a broad/multi-part question... use deep_research'). This is clear, actionable routing guidance with no ambiguity.

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