update_session

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the useful partial-update trait, but does not explain permissions, failure behavior for missing sessions, or whether null values clear fields or leave them 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 short sentences with zero waste. The mutation purpose and the partial-update rule are front-loaded.

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 mutation tool with no annotations, no output schema, and 0% parameter description coverage, the definition is too sparse. It leaves key details about workout_id, null handling, permissions, and failure modes unstated.

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 obliquely maps 'rename' to title and 'notes' to instruction, but never explains the required workout_id, and the term 'notes' does not match the schema parameter name 'instruction,' creating ambiguity.

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 states a clear mutation verb and resource: rename a session and/or set its notes. It is distinguishable from create_session/delete_session, though it does not explicitly differentiate update_session from update_block or set_prescription.

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?

It implies partial update behavior with 'Omitted fields stay unchanged,' but gives no explicit guidance on when to use this tool versus alternatives such as update_block or create_session. There are no prerequisites or exclusions.

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