edit_exercise_entries

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

Annotations already indicate readOnlyHint=false (mutation) and idempotentHint=false. The description adds the auth requirement, which is not in annotations, and clarifies the core behavior. It does not disclose error behaviors or limits, but goes beyond annotations.

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 with no wasted words. The first sentence describes the action, the second adds a critical prerequisite. Every sentence adds value.

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 7-parameter mutation tool without an output schema, the description explains the core action and auth requirement but omits details on optional parameters, return values, error conditions, or limits (e.g., what happens if insufficient minutes exist). Adequate but incomplete.

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 coverage is 57% (4 of 7 params described). The description adds meaning for shift_from_id, shift_to_id, and minutes by explaining the shifting operation, but does not address undocumented parameters like kcal, shift_to_name, shift_from_name. It partially compensates.

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 verb 'shift' and resource 'exercise time between activities', and specifies it moves minutes from one exercise to another. This is specific and distinguishes it from sibling tools, none of which perform this operation.

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 notes a prerequisite (profile auth and check_auth_status) but does not explicitly discuss when to use vs alternatives. However, as the only tool for shifting exercise minutes, the context is clear enough to guide usage.

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