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

Annotations already flag destructiveHint=true, so the bar is lower, yet the description adds real value beyond them: it discloses the three-open-briefs capacity being freed and, critically, that a dropped brief is 'never handed out again' — an irreversibility guarantee the annotations don't encode. It stops short of saying whether the brief's content/notes are recoverable.

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?

Two sentences, no waste, with the resource/scope front-loaded and the capacity/irreversibility consequences in the second sentence.

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 two-parameter, no-output-schema tool this covers the essentials: what it targets, the capacity effect, and irreversibility. The only missing piece an agent might want is confirmation of what happens to the dropped brief's stored content or a return indication of success.

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% and both parameters are documented, including the useful cross-reference that the id comes from mttr_content_next. The description restates 'by its id' and the site scoping without adding format or constraint detail beyond the schema, so baseline 3 applies.

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 resource ('Drops ... content briefs') plus scope ('one of your open ... for a site, by its id'), which separates it from mttr_content_next (fetch a brief) and mttr_content_done (finish one).

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 phrase 'one of your open content briefs' implies a prerequisite (a brief must currently be open), but the description never states when to drop versus complete via mttr_content_done, nor any conditions/exclusions. Usage is inferred rather than guided.

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