sync_workouts

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

Although no annotations are provided, the description compensates fully. It discloses that the sync is 'delta by default and cheap to call,' that full mode 're-fetches everything and reconciles deletions,' and that it also refreshes templates and measurements, revealing side effects and cost.

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?

Four sentences, each earning its place: purpose, usage timing, parameter explanation, and additional scope. The text is front-loaded with the main action and free of fluff.

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 one-parameter sync tool with no output schema, the description covers what, when, why, and the parameter's behavioral difference. It leaves no gaps that would hinder an agent from correctly selecting and invoking the tool.

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 0% for the single parameter, so the description must explain it. It does: 'Delta by default' (full=False) and 'full=True re-fetches everything and reconciles deletions,' adding substantial meaning beyond the bare boolean field.

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 opens with 'Pull new training data from Hevy into the database,' clearly stating the action and resource. It also notes it refreshes exercise templates and body measurements, and the sibling tools are all food/query tools, so there is no confusion about what this tool does.

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?

Explicitly instructs to 'Call this before answering a question about recent training,' grounding when to use it. It also distinguishes delta vs full mode: 'use it only if the data looks wrong, not routinely,' providing a clear exclusion for full mode and guiding appropriate invocation.

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