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

Annotations already set destructiveHint: true. The description adds important behavioral context: delete_session is irreversible, delete_routine is reversible (soft-delete), and bulk support. It does not describe return format or side effects, but the destructive nature and irreversibility are clearly stated.

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 reasonably structured with a list of actions and a flattened action note, but it includes extraneous details about other actions that are not the primary function. Could be more concise by focusing solely on delete_session and moving sibling actions to a 'see also' note.

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 tool with 7 parameters and no output schema, the description covers key aspects: irreversibility, relationship to other tools, and parameter sourcing for exercise_session_id. Missing details on account and single-id parameters, but bulk support is well described. Adequate for an agent to invoke correctly.

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 must compensate. It adds context for exercise_session_id by referencing another tool, and mentions bulk parameters (routine_ids, session_ids, exercise_session_ids). However, it does not explain account, routine_id, session_id, or the exact role of each parameter. Partial improvement over the bare 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?

The description clearly states the tool performs 'delete_session', but it also lists other destructive operations (delete_routine, delete_exercise) which are handled by sibling tools. The 'Flattened action: delete_session' clarifies the intended action, but the extraneous list may cause confusion. Distinguishes from siblings as a session-specific deletion tool.

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 implies that this tool is for delete_session via 'Flattened action: delete_session', but does not explicitly state when to use it versus sibling tools for routine/exercise deletion. No guidance on prerequisites or when not to use. Bulk support mention is useful but insufficient for clear usage direction.

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