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

Annotations are all false, providing no safety/behavioral signals, so the description carries the full burden. It discloses meaningful behaviors beyond the obvious send action: filing returns a claim_token for later inquiry, invocation with claim_token alone reads status, rate limiting (5/day/identifier), quota exemption, and operational cadence (digests read daily). This gives the agent a clear behavioral model without contradicting 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 but nearly every sentence adds operational value, from the core purpose in the first sentence to the rate limit and quota note at the end. It is front-loaded and well-ordered, but slightly verbose with motivational context ('signal directly affects roadmap') that, while useful, is not strictly necessary.

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 4 parameters, no output schema, and nuanced usage rules, the description fully covers the tool's lifecycle: what it does, when to use it, what to avoid, how to follow up with a claim_token, and rate limits. The nested context object is explained in the schema, and the description compensates for the missing output schema by describing the token return. Nothing significant is left unaddressed.

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?

Although the schema covers 100% of parameters with descriptions, the description adds semantics beyond schema: it explains the claim_token lifecycle concretely with an example call, and instructs what the message should contain ('Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt'). This elevates the minimal value above the baseline 3.

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 immediately enumerates the exact feedback types (bug, feature/data_gap, praise), making the tool's scope unmistakable. This clearly distinguishes it from all sibling tools, none of which are feedback-related.

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?

Explicit when-to-use guidance is provided: '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 gives a strong when-not-to-use with a specific alternative: 'if the tool came from a different MCP server... file it with that server instead.' This is model behavior for usage guidance.

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