add_bike

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

With no annotations, the description bears full burden. It discloses parameter constraints but does not mention side effects, error behavior, or where the step is added (e.g., appending to current workout).

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 plus a bulleted parameter list. Each sentence provides essential information. No 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?

Covers parameter constraints well, but does not explain the return value or how the step integrates into a workout. Output schema exists but is not referenced in description.

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%, but the description compensates fully: it provides format notes ('M:SS', '10km'), pairing rules (power_min with power_max), and constraints (set exactly one end condition).

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 starts with 'Add a cycling interval step,' providing a clear verb and resource. It distinguishes from siblings by specifying 'cycling' and outlines end condition and target constraints.

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 gives explicit rules for end condition and target, telling users what combinations are allowed. However, it does not compare to other add tools in the sibling list, leaving the context of choosing this tool over others implicit.

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