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

Annotations provide no behavioral hints (all false), so the description carries the full burden. It discloses rate limiting ('5 per identifier per day'), cost ('Free; doesn't count against your tool-call quota'), the claim_token flow (filing without an account returns a token; passing it back later retrieves status), and that the team reads digests daily. This goes well beyond the bare 'send feedback' implied by the 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 long (~250 words) but information-dense. It front-loads the purpose in the first sentence and then systematically covers use cases, exclusions, claim-token mechanics, and rate limits. No sentence is purely filler, though it could be tightened without losing clarity; it is near the upper limit of acceptable length for such a feature-rich feedback tool.

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, so the description must explain return behavior. It does explain the claim_token return and its later use, and clarifies non-account behavior. It doesn't describe the response when an account is present or when a claim_token is not passed, but for a feedback submission tool this is a minor gap. Given the tool's low complexity and strong schema coverage, the description is sufficiently 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 value by explaining the claim_token lifecycle ('Filing without an account returns a `claim_token`; pass it back later... to read whether it was fixed'), and by guiding message content ('Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt'). These are not present in the schema's parameter descriptions, justifying a 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 opens with a specific verb and resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It then enumerates concrete use cases (bug, feature/data_gap, praise), clearly distinguishing this from sibling tools like ask_pipeworx or discover_tools, and further differentiates by scoping to 'tools served by this Pipeworx connection.' This leaves no ambiguity about what the tool does.

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 gives explicit when-to-use guidance: '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).' It also provides a clear when-not-to-use and alternative: if the tool belongs to a different MCP server, 'file it with that server instead,' and tells how to disambiguate ('Pipeworx tool names are the ones this connection lists').

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