Remember that the person said no

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

Annotations already establish that this is a non-read-only, idempotent, non-destructive operation. The description adds valuable behavioral context beyond the annotations by explaining the consequence: the declined item will not be offered again in this project, which scopes the effect.

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 well-formed sentence, front-loaded with the call condition and ending with the operational consequence. There is no redundant or filler language.

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 simple two-parameter mutation with complete schema coverage and annotations covering safety/idempotency, the description is complete enough: it says when to call it and what effect it has. It could be slightly stronger by clarifying the relationship between area and kind, but that is minor.

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%, so the enum for area and the kind constraints/examples are already fully documented in the schema. The description reinforces the kinds of things that may be declined, but adds little parameter-specific meaning beyond what the schema provides.

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 action (declining/remembering a refusal) and resource (something Trood offered), and explains the resulting state change: it will not be offered again in this project. It differentiates from offer-creation siblings by focusing on refusal rather than drafting or publishing, though it does not explicitly name those alternatives.

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?

It gives a clear trigger: call when the person turns down a Trood offer such as a tutorial, walkthrough, or check. It does not explicitly state when not to use it or name sibling tools, but the usage context is strong and actionable.

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