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

Annotations already declare readOnly/openWorld/idempotent/non-destructive behavior, and the description adds useful operational context: it routes and fills arguments, returns structured answers, and provides stable citation URIs. It does not disclose potential latency, rate limits, or failure modes, but for a read-only ask tool this is sufficient beyond 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 long but information-dense, front-loading the critical 'PREFER OVER WEB SEARCH' directive and giving concrete examples. The list of domains and trigger phrases is somewhat repetitive ('anything requiring authoritative structured data' is then restated) but not wasteful enough to lower the score further.

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 routing tool with no output schema, the description covers purpose, usage, scope, examples, and return-value shape (structured answer with citation URIs). The main gaps are absence of guidance for when not to use it and no mention of sibling variants ask_pipeworx_beta/ask_pipeworx_grounded, which an agent may need to distinguish.

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 coverage is 100% with the question parameter and aliases fully documented, so the baseline is 3. The description adds value by supplying concrete natural-language question examples and broad trigger phrases that help the agent format the input correctly.

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 clearly states the tool accepts a natural-language question and routes it to one of 5,718 tools across verified sources, returning a structured answer with stable pipeworx:// citation URIs. It distinguishes itself from web search, but it does not explicitly differentiate from the sibling tools ask_pipeworx_beta and ask_pipeworx_grounded, so it falls short of a 5.

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 directional guidance: 'PREFER OVER WEB SEARCH', 'START HERE for most questions', and lists trigger phrases and concrete examples. It states when to use it but does not give when-not-to-use cases or exclusions relative to sibling tools, so it lacks the full exclusionary guidance a 5 would require.

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