list_schedule_v3_rotation_events

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the return type ('List of events defining the on-call coverage windows and member assignments'), which provides useful context beyond the annotations. However, no additional behavioral traits are disclosed.

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 brief and well-structured, with a one-line purpose, followed by Args and Returns sections. No extraneous information; every sentence is necessary and front-loaded.

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 has two simple required parameters, a clear purpose, and an output schema (implied). The description explains the return value adequately: 'List of events defining the on-call coverage windows and member assignments'. All necessary context is provided.

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?

With 0% schema description coverage, the description elaborates on both parameters: 'schedule_id: The ID of the v3 schedule' and 'rotation_id: The ID of the rotation'. This adds meaning beyond the schema titles, which are just 'Rotation Id' and 'Schedule Id'.

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 explicitly states 'List all events for a rotation in a v3 schedule', using a specific verb and resource. It clearly distinguishes from sibling tools like 'list_schedule_v3_rotations' and 'get_schedule_v3_rotation_event'.

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 clearly indicates when to use the tool (to list events for a rotation). While it does not explicitly state when not to use it, the purpose is unambiguous and sibling names provide differentiation, making usage context clear.

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