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

Annotations are all false and offer no safety hints, 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... to read whether it was fixed'), rate limits ('Rate-limited to 5 per identifier per day'), and quota impact ('Free; doesn't count against your tool-call quota'). This is rich behavioral context beyond what annotations provide.

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 appropriately sized for the tool's complexity. It is front-loaded with the core purpose, then usage guidelines, exclusions, token mechanics, and operational notes. Every sentence adds distinct value — no filler or repetition. The logical flow from what → when → how → constraints is exemplary.

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 the tool's moderate complexity (nested context object, enum, conditional claim_token behavior) and the absence of an output schema, the description covers all critical aspects: what feedback types exist, how to provide context, the token-based response mechanism, rate limits, and scope boundaries. It is complete enough for an agent to invoke the tool correctly without further clarification.

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?

The schema already has 100% coverage of all 4 parameters, so the baseline is 3. The description adds meaning beyond the schema by explaining the claim_token usage in context ('pass the pwfb_… token that filing returned, with no other arguments') and clarifying the intended message specificity. This extra semantic guidance justifies a 4, though the schema does most of the heavy lifting.

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's purpose: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It specifies the resource (Pipeworx team), the action (tell/send feedback), and distinct categories (bug, feature, data_gap, praise). This distinguishes it effectively from all sibling tools, none of which are feedback-related.

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 provides explicit when-to-use guidance for each feedback type ('Use when a tool returns wrong/stale data... when a tool you wish existed isn't in the catalog... when something worked surprisingly well'). It also gives a clear exclusion: 'ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server... file it with that server instead.' This is ideal usage guidance with alternatives and exclusions.

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