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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds meaningful behavioral context beyond those annotations: it discloses that the tool routes to one of 5,743 tools, fills arguments, returns stable pipeworx:// citation URIs, works on every tier, and makes one fast call. No annotation contradiction exists.

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 its key directive and is well organized, but it is fairly long and contains some redundancy between the domain list and the later examples. Overall, nearly every sentence adds value, and the structure helps an agent parse priorities quickly.

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 having no output schema, the description explains what the tool returns (structured answer with stable citation URIs), when to use it, when to use alternatives, and what type of inputs are valid. For a broad router tool with one required parameter, this is complete enough 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 the baseline is 3. The schema already documents the question parameter and all aliases (query, q, prompt, text, input), and includes examples. The tool description adds no new parameter-level semantics beyond those 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 gives a specific verb and resource: it states that ask_pipeworx routes questions to the appropriate one of 5,743 tools and returns structured answers with citation URIs. It also clearly differentiates from siblings by naming ask_pipeworx_grounded and deep_research as the alternatives for different use cases.

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?

Usage guidance is explicit and actionable: it says to prefer this over web search for factual/current-data questions, provides example phrasings, and gives precise conditions for stepping up to ask_pipeworx_grounded or deep_research. This is the clearest possible when-to-use-versus-alternative guidance.

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