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

Annotations provide no safety signals (all false), so the description carries the burden. It adds meaningful behavioral disclosure: claim_token flow for anonymous filing, rate limit of 5 per identifier per day, no quota impact, and that reports are read daily. It could be even stronger by stating explicitly whether reports are stored or transmitted externally, but the given context is substantial.

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?

Though longer than typical tool descriptions, every sentence adds necessary information: purpose, usage categories, exclusions, claim-token mechanics, rate limits, quota impact, and roadmap signal. It is front-loaded with the primary purpose and structured logically from 'what' to 'when' to 'how', making it easy to scan.

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 no output schema, the description adequately covers return behavior by mentioning the claim_token returned on filing and the ability to later check status and changes. It handles the tool's complexity (4 parameters, nested context, multiple feedback types) well, and sibling tool context confirms this is a special-purpose tool that needs no cross-referencing to other tools.

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 covers all parameters with descriptions, so baseline is 3. The description adds valuable semantic context beyond the schema, especially for claim_token: it explains the full flow of receiving a token and passing it back later. It also offers guidance on message content (describe in terms of Pipeworx tools, don't paste user prompt), which enriches the understanding of the message parameter.

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 leads with a specific action ('Tell the Pipeworx team something is broken, missing, or needs to exist') and clearly identifies the resource (Pipeworx feedback). It distinguishes this tool from all sibling tools by framing it as the channel for reporting bugs, feature requests, data gaps, and praise, which is unique among the listed tools.

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?

Provides explicit when-to-use guidance via enumerated categories (bug, feature, data_gap, praise) and gives a clear exclusion criterion: only for tools served by this Pipeworx connection, not other MCP servers. It also explains when to defer and what to do when unsure, plus practical constraints like rate limits and daily digest.

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