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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: the exact return shape on success, the explicit refusal reasons list, and the 'uses ONLY what the tool result contains' constraint. It doesn't detail rate limits or pagination, but for a read-only Q&A tool the refusal contract is the key behavioral disclosure.

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 dense but well-organized: it front-loads the core behavior, then the return/refusal contract, then usage guidance and cost tradeoff. Every sentence earns its place, though the refusal-reason list is somewhat long and could be trimmed without losing meaning.

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 read-only Q&A tool with rich annotations and a fully documented schema, the description covers the essential context: what it does, when to use it, what it returns, and how it refuses. It doesn't explain the return format in detail beyond the shape, but no output schema exists, so the inline return shape is sufficient. The only minor gap is not elaborating on the 'same routing as ask_pipeworx' mechanism, but that's not needed to call it 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% and the schema already documents the 'question' parameter plus all aliases. The description adds the semantic context that the question is in natural language and that the tool fills arguments and fetches data, but it doesn't add syntax or format details beyond what the schema 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?

The description clearly states this is a hallucination-resistant answer mode for high-stakes reads, with a specific verb ('EXTRACTS the answer using ONLY what the tool result contains') and resource (the Pipeworx tool routing). It distinguishes itself from ask_pipeworx by name and by the explicit refusal behavior, so an agent can tell them apart.

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 when to use it ('whenever an answer will be quoted, cited, or acted on, and the agent must not invent facts') and when not to ('prefer ask_pipeworx for casual lookups'). It also names the sibling alternative (ask_pipeworx) and the cost tradeoff (one extra LLM call).

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