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

Annotations are all false, so the description carries the transparency burden. It discloses the claim_token flow, daily rate limit (5 per identifier per day), that it's free and doesn't consume quota, and that the team reads digests daily. It also explains how to check resolution status with claim_token, adding behavioral detail well beyond the annotation flags.

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 a single dense paragraph of ~170 words, but it is front-loaded with the purpose in the first sentence and every subsequent sentence delivers a distinct fact (types, exclusions, token flow, rate limits). While not broken into bullets, it is efficiently packed without redundant filler.

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 feedback tool with no output schema, the description covers all essential context: purpose, trigger conditions, exclusion boundaries, token-based follow-up mechanism, rate limiting, and how feedback is consumed. It even gives a concrete example of a claim_token format. This is a complete and self-contained explanation.

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?

Input schema has 100% coverage with descriptions for every parameter, providing the baseline of 3. The description adds meaningful extra semantics: it explains the claim_token lifecycle (filing without an account returns one, passing it back retrieves status), and instructs users to describe issues in terms of Pipeworx tools/packs rather than pasting end-user prompts, which supplements the message parameter schema.

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 opens with a clear action: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It specifies the resource (Pipeworx team) and differentiates from siblings by focusing on feedback about Pipeworx tools, not asking questions or research. The enumerated types (bug, feature, data_gap, praise) further clarify its scope.

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 explicitly states when to use the tool ('Use when a tool returns wrong/stale data... when something worked surprisingly well') and when not to ('if the tool came from a different MCP server... file it with that server instead'). It also provides a disambiguation rule based on tool name source, which is strong alternative guidance.

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