calculate_vdot

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

With no annotations, the description carries the full burden of explaining behavior, but it only states that it calculates a VDOT rating. It does not disclose what the output represents, any range or units, potential error cases, or assumptions about the race distance. The behavioral transparency is minimal.

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, concise sentence that conveys the essential purpose. It contains no filler or repetition, making it an example of efficient writing. Every word contributes 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?

The tool is simple with only two parameters, and the schema covers them well. However, no output schema exists, so the description should at least mention what the tool returns (e.g., a VDOT score). It also lacks context on how to use or interpret the result, leaving the implementation incomplete for an agent.

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 100% with both parameters described (distance in meters, time in seconds). The description adds the context 'race performance' but does not provide any additional meaning or relationships beyond the schema. Baseline 3 is appropriate when the schema already documents parameters clearly.

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 calculates a Jack Daniels VDOT rating from race performance. The verb 'calculates' is specific, the resource 'VDOT rating' is well-defined, and 'from a race performance' scopes the input. This distinguishes it from sibling tools that calculate other metrics like TID or threshold.

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 when a race result is available, but it does not explicitly state when to use this tool versus alternatives such as calculate_tid or predict_race. There is no mention of exclusions or alternative tools, but the 'race performance' context provides some guidance.

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