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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the danger signal is partly redundant, but the description adds real value: replace-all semantics (all existing sets are discarded, not merged) and that payload is sent verbatim. These specifics go beyond what the structured annotations convey.

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, front-loaded with the core operation and immediately followed by the risk warning. No filler; every clause carries signal.

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 mutation tool with annotations already covering the safety profile and no output schema, the description discloses the critical risk and the replace-all behavior. The main residual gap is the opaque payload shape, which is left unaddressed.

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 50%: activityId is documented ('Numeric id') but payload has no top-level description and its exerciseSets items are opaque ('Any JSON value'). The description clarifies how payload is applied ('sent verbatim', replace-all) but never explains its expected structure, so it only partially compensates for the coverage gap.

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 ('Replaces') and resource ('a strength activity's exercise sets'), with scope made explicit ('ALL'). This clearly distinguishes it from the read sibling get_activity_exercise_sets, so an agent can tell it is the write counterpart 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?

Gives one concrete usage rule ('IRREVERSIBLE: confirm with the user before calling'), which is genuinely actionable. However, it offers no guidance on when to use this tool versus alternatives and no prerequisites beyond the confirmation step, so usage is only partially covered.

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