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

Annotations are minimal (all false hints), so the description carries the burden. It discloses several behavioral traits: filing without an account returns a claim_token; passing it back later allows reading the status; rate-limited to 5 per identifier per day; free and doesn't count against tool-call quota; team reads digests daily. It also describes the conditional behavior of claim_token (read vs. file mode). This goes well beyond what annotations convey.

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 a single dense paragraph that front-loads the core purpose and gives concrete use cases. Every sentence earns its place, but it is slightly long and could be broken into shorter sentences or bullets for scannability. It is still concise relative to the amount of behavioral information conveyed.

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 feedback tool with no output schema and minimal annotations, the description is remarkably complete: it covers filing types, exclusions, claim_token return/read flow, rate limits, quota accounting, and team response cadence. It also warns against pasting end-user prompts. The nested context object is optional and well-described in the schema. No critical gaps remain.

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 extra meaning by explaining the claim_token flow ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed') and clarifies that claim_token can be used standalone with 'no other arguments.' It also explains the rate limit context. It doesn't fully compensate for the nested context object's semantics, but the schema already describes each field 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 states a specific verb+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It clearly distinguishes this from siblings by framing it as feedback about Pipeworx tools specifically, not a generic query or research tool. It also names the output behavior (returns claim_token) and the types of feedback accepted.

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 gives explicit when-to-use guidance: use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or for praise. It also provides an explicit exclusion: 'ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server... file it with that server instead.' This is strong differentiation from alternatives.

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