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

Despite annotations being all false (write, non-idempotent, etc.), the description adds rich behavioral context: rate-limited to 5 per identifier per day, free and doesn't count against quota, returns a claim_token for anonymous filing, and the team reads digests daily. This significantly exceeds the annotation signal and contains no contradictions.

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 (~150 words) but every sentence earns its place, covering purpose, exclusions, usage flow, and limitations. It is front-loaded with the core purpose and uses clear, direct language. Minor deduction only because it could be tightened without losing critical guidance, but the density of useful information justifies the length.

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 tool with no output schema and 4 parameters, the description fully covers behavior, return value (claim_token), rate limits, scope, and the reading-reply flow. It also addresses ambiguity around 'other' types implicitly. This is a self-contained explanation that leaves almost no user questions unanswered.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful value by demonstrating the claim_token usage pattern ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"})') and explaining the anonymous flow. It also reinforces the type enum meanings indirectly, though the schema already documents those well.

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 immediately distinguishes this tool from all siblings by enumerating the exact feedback categories (bug, feature, data_gap, praise) and explicitly scoping it to Pipeworx tools. This is unambiguous 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 ('returns wrong/stale data', 'wish existed', 'worked surprisingly well') and a strong exclusion: tools from other MCP servers should not be reported here, naming the correct alternative (file with that server). It also explains the claim_token flow for follow-up, covering both initial filing and later retrieval.

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