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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds real value beyond them: it clarifies full-replacement semantics, a hard validation rule ('At least one must be kind=hard'), and the id-preservation trick ('Pass existing ids to keep them'), which is exactly the behavior an agent needs to avoid clobbering data. It still does not say what happens to sessions classified under removed levers.

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?

Three compact sentences, front-loaded with the replace action, then the validation constraint, then field hints. Dense but each sentence carries information; no filler.

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 destructive, single-parameter replace tool with no output schema, the description covers semantics, validation, and the id-preservation pattern needed to avoid unintended destruction. Minor gaps remain (fate of sessions tied to removed levers, required 'name'), keeping it short of a 5.

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%, so the description carries the burden, and it does: it explains id (pass to keep), kind (must include hard), and that keywords/repos are classification hints from session task text. It omits 'name' and 'examples', but those are self-evident from the schema.

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 ('Replace the list of levers') and even defines the domain term ('the recurring kinds of goal work'), which is not obvious from the name alone. It aligns with the set_* sibling family but does not name any sibling to differentiate itself explicitly.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of alternatives like set_commitments, set_plan, or set_routines that also replace list-like state. The replacement semantics are implied by 'Replace the list' but an agent gets no routing help.

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