garmin_create_scheduled_workout

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

With no annotations, the description must disclose behavioral traits but only states the basic action sequence. It does not mention side effects (e.g., overwriting existing schedules), authentication requirements, validation rules, or error handling. The tool's behavior remains opaque.

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 a single, front-loaded sentence that directly states the tool's function without wasting words. However, it could be restructured to include brief usage notes, but it remains efficient.

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?

Despite having an output schema, the description lacks details about the workflow (e.g., atomicity of upload and schedule), error conditions for invalid JSON, and what happens if the date is in the past. For a tool requiring structured input, this is insufficient.

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 adds the date format 'YYYY-MM-DD' for the 'day' parameter, which is not in the schema. For 'workout_json', it only says 'workout JSON payload,' offering minimal additional meaning. Since schema coverage is 0%, the description partially compensates but leaves the expected structure of workout_json unspecified.

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 both actions: 'Upload a Garmin workout JSON payload' and 'schedule it on a YYYY-MM-DD date.' The verb+resource combination is specific, and the mention of scheduling distinguishes it from sibling tools like garmin_workouts or garmin_schedule_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 context (upload and schedule a workout) but does not explicitly state when to use this tool versus alternatives like garmin_schedule_workout (which may only schedule existing workouts) or garmin_unschedule_workout. No exclusion criteria or prerequisites are provided.

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