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

With all annotations set to false (no read-only, idempotent, or destructive hints), the description carries the transparency burden. It discloses key behaviors: anonymous filing returns a claim_token, that token can be used later to check status and fixes, rate limiting to 5 per identifier per day, and that it doesn't count against tool-call quota. This goes well beyond the generic expectations for a feedback tool.

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 a typical tool description but is information-dense, with every sentence serving a purpose: purpose, use cases, exclusions, content guidance, claim_token workflow, rate limits, and quota impact. It's front-loaded with the core purpose and remains highly readable as a single paragraph. A slight ding for length, but no 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 that there is no output schema, the description covers all necessary context for successful use: what to report, how to phrase it, what happens after filing (claim_token), how to check status, rate limits, and importantly, which tools this applies to. For a feedback tool, this is complete and leaves little ambiguity.

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 has 100% parameter description coverage, so baseline is 3. The description adds extra semantics for claim_token, explaining the anonymous-filing round-trip workflow in a way the schema's short description does not. It also reinforces the message parameter guidance. This added value raises it above baseline, though not to a 5 since not every parameter gets special treatment.

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 statement of purpose: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It lists specific feedback categories (bug, feature/data_gap, praise) and distinguishes this tool from sibling ask_pipeworx tools, which are for asking questions, not submitting feedback. The verb 'tell' and resource 'Pipeworx team' make the action 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?

The description provides explicit usage guidance, including exactly when to use the tool (bug, feature/data_gap, praise) and, crucially, when not to: if the tool came from a different MCP server, file with that server instead. It also instructs to describe issues in terms of Pipeworx tools/packs and not to paste the end-user's prompt, giving clear context for appropriate use.

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