unschedule_workout

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 known. The description adds the crucial detail that only the calendar entry goes and the underlying template persists, which the annotations cannot express, plus an explicit confirmation requirement.

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?

A single front-loaded sentence with no wasted clauses; the destructive consequence leads. Minor deduction for the redundant, oddly capitalized 'irreversible IRREVERSIBLE' repetition that mildly muddies the structure.

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 one-parameter destructive tool with annotations covering the safety profile and no output schema, this covers the essential agent-facing facts. It omits what happens if the scheduledWorkoutId is invalid or not found, a small remaining gap.

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?

Only one parameter, and the schema at 100% coverage documents it as 'Numeric id'. The description adds no type, format, or lookup guidance beyond that, so the baseline 3 applies.

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+resource ('removes the calendar entry') and immediately disambiguates scope from the sibling delete_workout by noting the workout template is preserved. An agent can distinguish this from delete_workout and delete_calendar_event without opening a 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 a clear operational directive ('confirm with the user before calling') and implies when this is preferred over delete_workout by stating the template survives. It stops short of explicitly naming alternatives or the condition that would pick delete_workout instead.

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