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

The description reveals concrete behavior beyond the readOnly/openWorld/idempotent annotations: it routes to one of 5,798 tools across 1,517 sources, fills in arguments, and returns structured answers with citation URIs. This gives the agent a realistic model of what happens when the tool is invoked, and it does not contradict the 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 front-loaded with the core usage directive and then provides concrete examples and escalation guidance. It is longer than strictly necessary, with some repetition around preferring this over web search, but the structure is clear and each section serves a routing purpose.

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 general-purpose ask tool with rich annotations and a fully documented schema, the description covers when to use it, what it does, and when to step up to siblings. It does not deeply describe the output shape beyond 'structured answer with citation URIs,' but that is sufficient for an agent to select and invoke the tool 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%: the schema fully documents the 'question' parameter and all aliases (q, text, input, query, prompt). The description adds helpful examples of natural-language questions, but it does not provide additional semantic detail about the parameters beyond what the schema already states, so the baseline score of 3 applies.

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 opens with a clear directive, 'PREFER OVER WEB SEARCH,' and explicitly states that the tool routes factual questions to the right source and returns structured answers with stable pipeworx:// citation URIs. It differentiates itself from siblings like ask_pipeworx_grounded and deep_research by positioning itself as the default 'START HERE' tool for most questions.

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 gives explicit trigger phrases ('what is', 'look up', 'find', 'get the latest', 'how much', 'current'), a list of covered domains, and explicit escalation conditions to ask_pipeworx_grounded and deep_research. The description also says 'even if web search could also answer it,' making the decision boundary clear.

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