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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally; the description adds genuine value beyond that by disclosing blast radius ('affects everyone') and irreversibility ('PERMANENT'), plus the important behavioral fact that the call proposes rather than performs. It does not cover permissions or what the proposal record looks like, which keeps it below the top score.

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 mutation scope front-loaded and the propose-only caveat immediately after. Capitalized emphasis on 'PERMANENT' communicates risk efficiently without extra clauses.

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 one-parameter mutation with no output schema and full annotation coverage, the description supplies the essentials: what it targets, who it affects, that it is irreversible, and that it is only a proposal. The remaining gap is the follow-up path (how the proposal gets confirmed or discarded), which the agent must infer from siblings.

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 0% for the single event_id parameter, so the description has to compensate; 'by id' at least establishes that the integer must identify a household event rather than any other entity type. It adds no guidance on where the id comes from, whether it must belong to the household, or what happens with an invalid id.

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 names a specific verb and resource ('Propose cancelling a SHARED household event') plus the keying parameter ('by id'), and it distinguishes itself from a real cancellation by flagging 'Proposes only'. It stops short of naming the sibling that would execute the cancellation (e.g. confirm_change), so sibling differentiation is implied rather than explicit.

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?

Usage context is clear: this is for shared household events, and the note that it only proposes tells the agent this is step one of a two-phase flow rather than the final action. It gives a strong implicit 'when not' (do not expect deletion to happen here) but never names the follow-up or alternative tool to use instead.

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