get-workout-events

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

Reveals paging and ordering (newest to oldest) and event types, but omits details like response structure, error handling, and prerequisites. Since no annotations are provided, the description carries full burden; it covers core behavior but misses some important aspects.

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 concise sentences with no redundancy. The first states function, the second explains purpose. Front-loaded and 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?

Covers core functionality and use case, but without an output schema, it lacks details on the returned event objects field names and structure. This is adequate for a simple sync tool but could be more informative for integration decisions.

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?

Mentions 'since a given date' and 'paged list', adding meaning to the since, page, and pageSize parameters beyond the schema. However, it does not explain default values, boundaries, or the exact format required for 'since', and schema coverage is 0%, so more detail would be beneficial.

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 verb 'Retrieve', the resource 'workout events', and scope 'updates or deletes since a given date', differentiating it from sibling tools like get-workout and get-workouts that fetch full lists.

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 states the intention for cache synchronization, implying when to use it. However, it does not explicitly exclude other use cases or mention alternatives among siblings.

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