update-workout

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

No annotations present, so the description must convey behavioral traits. It mentions mutation and return of updated workout but does not disclose side effects, permission requirements, or how missing optional fields are handled (e.g., are they overwritten? left unchanged?).

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?

Two sentences, no redundant words, front-loaded with the action. Efficient and clear.

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 the complexity (7 parameters, nested exercises) and no output schema, the description is insufficiently complete. It does not clarify behavior for partially updating fields or how the exercises array is handled (replace vs merge).

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 description lists the major parameter categories (title, description, times, privacy, exercises), adding some meaning beyond the schema, but does not explain specific constraints or the structure of nested exercise objects. With 0% schema coverage, more detail is expected.

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 identifies the tool as updating an existing workout by ID, lists the modifiable fields (title, description, times, privacy, exercises), and states the return value. This distinguishes it from create-workout and other tools.

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?

No guidance on when to use this tool versus alternatives, no prerequisites (e.g., workout must exist), and no exclusions. The description is purely functional without context.

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