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

Annotations provide no safety hints (all false), so the description carries the full burden. It discloses the claim_token flow ('Filing without an account returns a claim_token; pass it back later...'), rate limiting ('Rate-limited to 5 per identifier per day'), cost ('Free; doesn't count against your tool-call quota'), and human processing ('The team reads digests daily'). No contradictions with 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?

Although the description is relatively long (~200 words), every sentence contributes a distinct piece of information: purpose, usage cases, exclusions, claim_token mechanics, rate limit, and cost. It is densely packed with no filler, and the key purpose is front-loaded in the first sentence. The structure flows logically from what → when → how → caveats.

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 tool with 4 optional params, a nested object, and no output schema, the description explains the key workflow: returning a claim_token and later reading the fix status by passing it back. It also specifies the types of feedback and exclusions, making the tool fully usable. The description adequately covers the output behavior (claim_token) without needing a formal output schema.

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%, so baseline is 3. The description adds semantics beyond the schema: it explains how to use claim_token (pass it back with no other arguments), clarifies that message should be specific and not paste the end-user's prompt, and guides context using 'Pipeworx tools/packs'. These are genuinely useful extras that help the agent choose correct parameter values.

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 starts with a clear, specific purpose: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It then enumerates the exact types of feedback (bug, feature/data_gap, praise), and explicitly distinguishes this tool from siblings by limiting scope to 'tools served by this Pipeworx connection' and contrasting with other vendors' connectors. This leaves no ambiguity about what the tool does or how it differs.

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?

The description gives precise 'when to use' conditions: 'Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise).' It also provides an explicit exclusion: 'if the tool came from a different MCP server... file it with that server instead.' The 'Not sure?' test ('Pipeworx tool names are the ones this connection lists') is a concrete decision rule.

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