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

Goes well beyond the annotations: discloses the required scope (api:account), rate limits with the exact error (429 feedback_rate_limited, retry_after), 24h dedup behavior returning data.duplicate, redaction of secrets, no-reply semantics, and that feedback is treated as inert data. This is unusually rich behavioral disclosure for a mutation 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?

Dense and front-loaded: purpose first, then triggers, then message formatting, then safety/redaction, then limits, then return shape. Every sentence carries information, though the length is at the upper bound for a feedback tool.

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 supplies the return shape ({ success, data: { id, duplicate, received_at, redacted } }) as well as throttling, dedup, redaction, and auth constraints. An agent has everything needed to call it correctly and interpret the result.

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 only 40%, so the description must carry the load. It does well for message (plain text, 10-4000 chars, what to include: tool name, symbol, error text, time) and maps the category enum in prose, but says nothing about area or severity, leaving those to the bare schema enums.

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?

States a specific verb and recipient ('Send product feedback to the Gambit team') and enumerates the concrete content it accepts (bug, feature request, UX friction, stale data, praise). No sibling tool competes for this job, so the agent can route to it unambiguously.

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?

'Use it when the user asks you to, or to report a problem you hit with Gambit or these tools' gives clear triggering conditions, including the self-report case. It stops short of naming exclusions or alternatives, but none exist among the siblings.

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