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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, lowering the bar for the description. The description adds useful context beyond annotations: it routes to one of 5,724 tools, fills arguments automatically, and returns structured answers with stable pipeworx:// citation URIs. It does not discuss rate limits or failure modes, but the annotation coverage makes this a minor gap.

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 front-loaded with the most important routing instruction ('PREFER OVER WEB SEARCH') and organized into clear guidance: when to use, examples, and when to escalate. It is longer than the minimum, but every sentence adds either routing guidance, examples, or sibling differentiation; only slight redundancy around 'current' and 'factual questions' prevents a 5.

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 low-parameter tool with rich annotations and no output schema, the description covers what an agent needs to choose and invoke it correctly: trigger phrases, example queries, behavior, output citation format, and escalation paths. Nothing essential is missing for successful selection and use.

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 covers 100% of parameters and documents that question accepts aliases (query, q, prompt, text, input), so the description does not need to add much. The examples do reinforce the question format, but the description adds no deeper semantic explanation beyond what the schema already provides. Baseline 3 is appropriate.

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?

States a specific verb-resource pair ('Ask Pipeworx') and a precise scope: factual questions about real-world entities and numbers across a broad set of categories. It distinguishes itself from siblings by naming ask_pipeworx_grounded and deep_research as alternatives, so the agent can tell them apart without opening their 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?

Explicitly says 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and gives exact step-up conditions for ask_pipeworx_grounded and deep_research. It also lists concrete example queries and covers the breaking-news edge case, leaving no ambiguity about when to choose this tool.

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