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

Beyond the annotations (readOnlyHint=false, etc.), the description discloses meaningful behaviors: rate limiting (5 per identifier per day), cost (free, no quota), return behavior (claim_token when no account), and the process (team reads digests daily). None of this contradicts the annotations; it substantially enriches what the agent can infer.

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 every sentence carries distinct information: purpose, use cases, exclusions, token mechanics, rate limits, and cost. It is well-structured and front-loaded with the core purpose. It could be slightly trimmed, but the density is high and no sentence is 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?

Given the tool's complexity (4 parameters, nested objects, no output schema), the description fully covers what the agent needs to know: what the tool does, when to use it, what to avoid, how the claim_token workflow operates, and the operational constraints. There are no significant gaps in understanding.

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 parameter's purpose and usage pattern (passing it back to read resolution status), and by framing the type enum's categories in terms of real feedback scenarios. This goes beyond the raw schema descriptions without duplicating them.

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+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It then enumerates concrete use cases (bug, feature, data_gap, praise), making the tool's purpose unmistakable and clearly distinct from sibling tools, none of which are feedback tools.

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 examples for each feedback category, and gives a critical exclusion: only for Pipeworx-owned tools, not other MCP servers. It also tells users when not to use it ('file it with that server instead') and how to handle claim tokens, making the decision boundary exceptionally clear.

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