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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=false, so the safety profile is covered; 'Sends nothing' largely restates openWorldHint=false. The description does not explain what destructive means here — whether marking done archives the item, whether the change is reversible, or what permissions are needed.

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 action set is front-loaded in a single sentence and closed with a short, useful constraint ('Sends nothing'). Slight redundancy with the action enum keeps it from a 5, but no sentence is wasted.

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 7 parameters fully documented in schema, annotations present, and no output schema to explain, the description covers what an agent needs to select the tool. The remaining gap is the absence of any reversal/aftermath note on a destructive mutation.

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 every parameter including the action enum and the note/reason/later/until dependencies is already documented. The description's action list mirrors the schema's own enum description and adds no syntax, format, or coupling detail beyond it; 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 specific verbs (mark done / not_needed, snooze, set/clear due) against a named resource ('one Needs you item'), which cleanly separates it from the read-oriented siblings list_work and get_work. An agent can identify the tool without opening the schema.

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?

'when the user asks' establishes the trigger context, and the action enumeration implies which case maps to which operation. There is no explicit when-not guidance or pointer to alternatives (e.g., use get_work/list_work to find the id first), which keeps it below a 5.

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