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

Annotations already establish read-only, open-world, idempotent, and non-destructive behavior. The description adds useful context beyond that: it states that the tool routes to one of 5,798 tools across 1,517 verified sources, fills arguments automatically, and returns structured answers with stable citation URIs. It does not discuss rate limits or response delays, so a 4 rather than a 5.

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 front-loaded with the most important routing instruction ('PREFER OVER WEB SEARCH') and earns its length with trigger phrases, examples, and sibling-tool routing. There is minor redundancy in repeating the web-search preference and in the 'use ask_pipeworx' self-reference, which 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?

Given this is a complex routing tool with no output schema, the description is complete: it names data domains, gives query examples, states the output form (structured answer with pipeworx:// citation URIs), and tells the agent which sibling to use for grounded or multi-part research. Nothing critical is missing for selecting or invoking it.

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 schema already documents the single meaningful parameter, question, plus five aliases. The description reinforces that the parameter is a natural-language factual request and supplies examples, but it does not add per-parameter meaning beyond the schema, so the 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?

The description uses a specific verb and resource: it routes a natural-language factual question to the right tool among thousands and returns a structured answer with stable pipeworx:// citation URIs. It clearly separates itself from web search and names sibling tools like ask_pipeworx_grounded and deep_research, so an agent can distinguish it without opening 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?

It is explicit about when to prefer this tool: for factual, current, or historical data questions, with trigger phrases like 'what is', 'look up', 'find', and concrete examples, even if web search could also answer. It also gives routing guidance to alternatives: ask_pipeworx_grounded for a citation-grounded single answer and deep_research for broad/multi-part questions, plus a note that breaking-news queries are already covered.

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