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

All annotation hints are false, so the description carries the full burden of behavior. It discloses several non-obvious behaviors: filing without an account returns a claim_token for later status reads, rate limiting to 5 per identifier per day, and that it's free with no impact on tool-call quota. No contradiction 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?

The description is front-loaded with the primary purpose and maintains a logical flow from usage to exclusions to token mechanics. However, it includes a few non-essential details such as 'The team reads digests daily and signal directly affects roadmap' that do not affect how an agent should invoke the tool, making it slightly longer than strictly necessary.

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?

Despite lacking an output schema, the description explains the return flow (claim_token for anonymous filing and later status reads), rate limits, scope limitations, and cost, which fully covers the key operational aspects. The rich schema covers parameter details, and the description adds all contextual behavior needed for correct invocation.

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 provides 100% coverage with rich descriptions for all four parameters, so the baseline is 3. The description adds extra meaning by warning not to paste the end-user's prompt (message parameter) and providing a concrete invocation example for the claim_token parameter (`pipeworx_feedback({claim_token:"pwfb_…"})`), which goes beyond the schema's text.

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, specific verb+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It distinguishes itself from sibling tools by scoping to 'tools served by this Pipeworx connection' and explicitly excluding feedback for other MCP servers, making it unambiguous.

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?

Explicitly lists triggers for each feedback type ('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)') and gives a clear exclusion for tools from other MCP servers with the alternative instruction to 'file it with that server instead.' It also advises how to phrase the message in terms of Pipeworx tools/packs.

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