Delete a to-do

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

Goes well beyond the destructiveHint/readOnlyHint annotations: it discloses irreversibility, the exact success string, the mandatory owner-approval gate and its 'Waiting for approval in Sara' response, and the 'turned off' outcome. This is precisely the operational context an agent needs before attempting a destructive call.

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?

Front-loaded with the action and a one-line sibling contrast; every sentence carries usable information. It is dense — the availability and approval clauses are stacked in long sentences — but nothing is truly 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?

For a single-parameter destructive tool with no output schema, it covers return values, irreversibility, approval gating, error path (via schema), and availability conditions. An agent has everything needed to call it and interpret the result.

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 the schema already explains that id is 'the number after # in list_tasks or get_today's results', so the description's mention of the id source is largely redundant. Nothing is added about the integer constraint or the refusal-on-unknown-id behavior beyond what the schema states.

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 ('Delete one of the owner's to-dos from Sara's planner ... by its id') and immediately distinguishes itself from the nearest sibling by contrasting deletion with complete_task's ticking-off. An agent can tell exactly what this does without inspecting 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?

Explicitly names the alternative ('to tick a to-do off instead, use complete_task') and the id source ('from list_tasks or get_today'). It also states the availability precondition (the owner must enable 'Let other apps change things'), which is real when-to-use guidance.

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