Log workout

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

No annotations are present, so the description bears the full burden. It discloses the core action (create/update completed workout) and the ID requirement, but lacks details on update mechanics, authentication needs, or behavioral traits like idempotency.

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 extremely concise: two sentences that front-load the purpose and a key constraint. Every word earns its place without superfluous information.

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 tool's complexity (nested objects, many fields, update capability), the description is too brief. It omits guidance on using update fields, linking to search tools, or explaining the required time fields for completed workouts.

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?

Despite 0% schema description coverage, the description adds value by clarifying that exerciseId in the nested object must be Ryot IDs, not names. However, it does not explain the complex nested structure or other critical parameters like updateWorkoutId.

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 tool creates or updates a completed Ryot workout, specifying the need for Ryot exercise IDs. This distinguishes it from other workout-related tools like ryot_log_minimum_workout or ryot_start_today_routine.

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 that exercise IDs must be obtained via ryot_search_exercises, but it does not explicitly compare to alternatives or state when to create vs. update. No exclusions provided.

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