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

With no annotations provided, the description carries full burden and satisfies it: it discloses that the tool 'Replaces any previous proposal wholesale,' that it is the only write for the scheduled run, and that changes are gated behind user review ('nothing here reaches the list until the user reviews and accepts it'). It also states the 100-delta limit, covering key behavioral constraints.

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 description is two sentences, front-loaded with the core purpose, and every phrase adds value: the replacement behavior, the exclusive write context, the review gating, and the 100-delta limit. There is zero redundancy.

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?

Given the tool's complexity (multiple delta kinds, rules, parameters) and the absence of annotations or output schema, the description provides essential context: it orients the agent on when to use it, the wholesale replacement semantics, and the critical safety property that nothing reaches the list until user acceptance. The rich schema covers the remaining detail, so the description is complete enough for selection and invocation.

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%, and the schema itself provides exhaustive descriptions for all parameters, including the delta kinds, field meanings, and constraints. The tool description adds only a brief contextual note about the 100-delta cap and wholesale replacement, which is already implied by the schema's description of deltas. Per the rubric, a baseline of 3 is appropriate when the schema does the heavy lifting.

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 uses a specific verb + resource: 'Replace the pending set of suggested changes.' It clearly distinguishes itself from sibling tools like add_item or complete_item by stating it is 'the ONLY write the scheduled run should make' and that it replaces the entire proposal wholesale, not just a single delta.

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 description explicitly states when to use: 'This is the ONLY write the scheduled run should make.' It contrasts with alternatives by noting that 'nothing here reaches the list until the user reviews and accepts it,' implying this is for proposing changes rather than direct mutation. It also gives a practical limit: 'up to 100 deltas,' which guides how to prioritize.

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