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

Annotations provide no hints (all false), so the description carries the full burden. It discloses the claim_token workflow (returned when filing without an account, reusable to read resolution), the team's daily digest review, the 5-per-day rate limit, quota exemption, and the scope restriction to this Pipeworx connection. This is rich behavioral disclosure far beyond what annotations offer.

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?

Though the description is long, every sentence earns its place: purpose, use cases, exclusion scope, formatting instructions, token behavior, and rate limits. It is front-loaded with the core function and then layers details in logical order, making it appropriately sized for the tool's complexity.

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?

With no output schema, the description must explain return values, and it does: it states that filing without an account returns a claim_token and explains the follow-up call to retrieve resolution. It also covers the four feedback types, scope boundaries, operational limits, and the relationship to the schema's nested context object. This is complete given the tool's complexity.

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% and each parameter already has a description, so the baseline is 3. The description adds meaningful context for the claim_token parameter by explaining how to pass it back to read whether the report was fixed, and hints at the context parameter usage ('describe the issue in terms of Pipeworx tools/packs'). This extra usage context justifies 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 clear, specific verb phrase 'Tell the Pipeworx team something is broken, missing, or needs to exist,' and immediately enumerates distinct use cases (bug, feature/data_gap, praise). This distinguishes it sharply from the sibling research/search tools and makes the tool's purpose 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 explicitly tells when to use the tool for each feedback type and, critically, when NOT to use it: it excludes tools from other MCP servers and directs the user to file with that server instead. It also provides formatting guidance (describe in terms of Pipeworx tools/packs, don't paste the end-user prompt), going well beyond basic usage.

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