get-workout-events

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

No annotations are provided, so the description carries the burden. It discloses that events are ordered newest-to-oldest, are limited to updates/deletes since a given date, and are paged. It also states the intended caching use case, providing useful behavioral context beyond the schema.

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, no fluff, front-loads the action and then adds purpose. Every word earns its place.

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 relatively simple, and the description covers purpose, ordering, event type, and use case. However, since there is no output schema, the description should also explain the structure of the returned events (e.g., fields per event) to fully enable the agent to use the data. This gap prevents a higher score.

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 descriptions are absent (0% coverage), so the description must explain parameters. 'since a given date' directly maps to the 'since' parameter, and 'paged list' implies page/pageSize usage. However, it doesn't detail parameter formats or default behavior beyond what's in the schema.

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 retrieves a paged list of workout events (updates or deletes) since a date, distinguishing it from get-workouts which would return the full workout list. The intentional mention of cache synchronization adds purpose specificity.

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 explains the use case: keeping a local cache up to date without fetching the entire list of workouts. This implies when to use this tool over get-workouts, though it doesn't explicitly name alternative tools or exclusion criteria.

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