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

Annotations already declare destructiveHint=true and readOnlyHint=false, so irreversibility is partly covered, but the description reinforces it and adds genuinely new context: the operation returns null on success (valuable since there is no output schema) and a required user-confirmation step. It stops short of saying whether the activity is recoverable or what happens to dependent data like gear links.

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?

Short and front-loaded, but repeats 'IRREVERSIBLE' twice, once as a bare fragment and again mid-sentence. The duplication wastes space and reads as boilerplate rather than deliberate emphasis, so it falls short of a clean, waste-free statement.

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?

With no output schema, the description correctly supplies the return behavior (null on success) and the destructive/confirmation requirement. For a single-parameter delete tool this is nearly complete; it would be fully complete with a note on recoverability or cascading effects.

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?

There is only one parameter (activityId) and schema description coverage is 100% ('Numeric id'), so the schema already carries the parameter documentation. The description adds nothing about the id format, yet accepts both integer and string per the schema, so an agent gets no extra clarification. Baseline 3 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?

States a specific verb (Deletes) and resource (an activity) in the opening sentence, clearly separating it from the many sibling delete_* tools (delete_workout, delete_course, delete_weigh_in) and from the set_/update_ activity tools. An agent can identify the correct tool 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?

The description gives one actionable usage rule: confirm with the user before calling. However, it never states when to prefer this over alternatives (e.g., deleting an activity vs. clearing a description via set_activity_description) or what preconditions exist. Usage guidance is present but thin.

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