delete_session

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

With no annotations provided, the description carries full burden. It only states 'Delete', which is already implied by the name. It does not disclose whether deletion is permanent or soft, any side effects on related data, or required permissions. For a mutation tool, this is insufficient.

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 a single sentence with no unnecessary words, achieving maximum conciseness while covering the essential purpose.

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 simple delete tool, the description is minimal. It omits behavioral details like reversibility, side effects, and return values. The ambiguity between 'program workout' and 'personal session' is not addressed, despite the parameter name only referencing 'program_workout_id'. Overall, an agent would struggle to know if this is a hard delete or if there are any conditions.

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?

The only parameter 'program_workout_id' has no description in the schema, so the description must compensate. It says 'by its ID', which indicates the parameter is the identifier, but it does not clarify the distinction between 'program workout' and 'personal session', nor does it specify the ID format or where to obtain it.

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 verb 'Delete' and the resource 'program workout / personal session', with the method 'by its ID'. It distinguishes from sibling tools like create_personal_session and log_workout by indicating a destructive operation.

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 does not provide any guidance on when to use this tool vs alternatives, when not to use it, or prerequisites such as ownership or permissions. There is no mention of conditions for deletion or any caution about irreversibility.

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