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

Annotations already declare non-destructive, idempotent, non-read-only, closed-world behavior, so the bar is lower. The description adds genuinely new context: the close is workspace-wide ('Closed for everyone in the workspace') and removes the item from resurfacing ('stop coming back'). What it omits is whether a close can be undone or reopened, which matters for a shared-state mutation.

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 short sentences, zero filler, with the action and the payoff front-loaded. Nothing is redundant with the title or annotations.

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 three-parameter mutation with no output schema, the description covers effect and blast radius (shared workspace) well. The remaining hole is operational rather than conceptual: which identifier form to pass and whether a close is reversible.

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?

Description says nothing about the parameters. With required=[] the agent gets no signal that at least one of item_id/item_ids must be supplied, and no guidance on choosing the singular id versus the plural array — the single most likely invocation error for this tool. The 67% schema coverage covers item_ids and project_id but leaves item_id undocumented and the mutual-exclusion rule unstated anywhere.

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?

Uses a specific verb ('Close') on a specific resource ('attention items') and frames the effect ('stop coming back'), which distinguishes it from the read-side sibling get_attention_items without naming it. It never explicitly names or contrasts a sibling, so it stops short of a 5.

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?

'Close attention items you've dealt with (or decided to leave)' gives a clear condition for use, including the deliberate-dismissal case. There is no when-not guidance and no named alternative (e.g. still use get_attention_items to review before closing).

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