update-workout

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds that the tool 'Returns the updated workout with all changes applied', which is useful but does not elaborate on additional side effects, authorization needs, or constraints beyond what annotations and schema imply.

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 two sentences (24 words), front-loaded with the core action, and contains no redundant or superfluous information. Every phrase adds necessary context.

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?

Given 7 parameters, a complex nested exercises schema, no output schema, and no parameter descriptions, the description is too minimal. It fails to explain update behavior (partial vs full replacement), optionality of fields, or exercise/set structure, leaving significant gaps for an AI agent.

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 carries the burden. It lists modifiable fields but does not explain parameter formats (e.g., ISO8601 for dates) or the structure of 'exercises' and nested objects. This adds marginal value over property names, earning a baseline score.

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 'Update an existing workout by ID' with a specific verb and resource, and enumerates modifiable fields (title, description, times, privacy, exercises). This distinguishes it from sibling tools like create-workout or get-workout.

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 usage by stating 'Update an existing workout' but does not explicitly guide when to use this tool versus alternatives like create-workout. No exclusions or prerequisites are mentioned, relying on the tool name for differentiation.

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