get_workout_events

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

With no annotations, the description carries the full burden. It explains pagination via page/page_size and the since parameter, but does not disclose behavior like rate limits, authentication, or empty results. Adequate but not rich.

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, front-loaded with purpose and resource type, then immediate usage guidance. No redundant or extraneous text. Highly 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?

Given the tool's simplicity (paginated event stream), with an output schema present to document return values, the description is nearly complete. It could mention ordering of events but is otherwise sufficient for correct invocation.

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?

Only the 'since' parameter has a schema description (33% coverage). The description adds ISO-8601 format guidance and an example for 'since', but page and page_size lack any semantic enrichment. The defaults mitigate but do not fully compensate.

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 it provides a 'stream of workout change events (created/updated/deleted)' and explicitly distinguishes its use case from siblings like list_workouts by emphasizing detection of new workouts without re-paginating.

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 a clear use case ('detect new workouts since a previous interaction') and implies not to use for full list. However, it lacks explicit when-not scenarios or alternative tool references beyond sibling list_workouts.

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