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

The annotations only provide generic hints (readOnlyHint=false, etc.), so the description carries the full burden. It discloses the claim_token flow (filing returns a token, passing it back later reads status and changes), rate-limiting (5/day), that it's free and doesn't count against quota, and that the team reads digests daily. There is no contradiction with annotations; on the contrary, the description adds vital non-obvious behavior beyond what annotations could convey.

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 longer than average, but it is front-loaded with the core purpose and every subsequent sentence adds distinct value: usage conditions, exclusions, token mechanics, rate limits. The sentence about roadmap signal is slightly motivational and could be trimmed, but overall it remains well-structured and not redundant. A 4 reflects the slight extra verbosity while acknowledging the appropriate length for the tool's complexity.

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?

There is no output schema, yet the description covers return behavior for both the initial submission (returns a claim_token) and follow-up (returns status and changes). It also covers rate limits, exclusions, and parameter usage context. For a simple feedback tool with unusual token flow, this description is remarkably complete.

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 the baseline is 3. The description adds meaningful context for the claim_token parameter by explaining the submission→token→follow-up lifecycle, and for message by advising to frame issues in terms of Pipeworx tools/packs. While the schema already describes each parameter well, this extra context nudges the score to 4.

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 begins with a clear, specific verb+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It enumerates concrete use cases (bug, feature/data_gap, praise) and explicitly distinguishes itself from sibling tools like ask_pipeworx by clarifying this is for reporting to the Pipeworx team, not for querying data. The purpose is unmistakable and well-differentiated.

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 with concrete triggers ('Use when a tool returns wrong/stale data...'), and explicit when-not-to-use guidance with an alternative ('if the tool came from a different MCP server... file it with that server instead'). It further disambiguates by advising 'Pipeworx tool names are the ones this connection lists.' This is a model of usage clarity.

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