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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety/duplication profile is covered. The description adds the key behavioral fact that text is transmitted to the MetricDuck team and clarifies the user-vs-model provenance handling, but says nothing about confirmation, rate limits, or irreversibility.

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?

Three short sentences, front-loaded with the gating condition, followed by parameter guidance and the action. No filler, nothing redundant.

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 3-param, no-output-schema, write-side tool the definition covers when to call, what is transmitted, and how to fill both non-obvious fields. Only minor gaps remain (no mention of confirmation or return behavior), and there is no output schema requiring explanation.

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 goes slightly beyond the schema by mapping real-world conditions onto the source enum ('user when the user wrote it, model when you summarised it') and instructing that message should carry the user's words, which reduces the chance of mis-filling.

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 (send) and resource (feedback/text to the MetricDuck team), and the title/name plus 'Sends the text to the MetricDuck team' make the action unmistakable. No sibling tool does anything comparable, so there is no ambiguity to resolve.

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, hard gating: 'Call ONLY when the user asks to send feedback to MetricDuck.' This is an unambiguous when-to-use constraint with an implicit when-not (do not call otherwise), which is exactly what an agent needs for a user-triggered side-effecting action.

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