list_schedule_v3_custom_shifts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, covering safety. The description adds context about the nature of custom shifts and the required time range. No contradictions.

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 concise with a clear definition followed by parameter list. Every sentence adds value, no redundancy.

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 an output schema exists, the description explains it returns a 'List of custom shifts in the specified time range.' All necessary information is present for a list operation.

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 explains all three required parameters: schedule_id (ID of v3 schedule), since and until (ISO 8601, required). This adds meaning beyond the schema which only provides type string and title.

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 'List custom shifts for a v3 schedule within a time range' and defines custom shifts as 'ad-hoc one-off shifts outside of rotation events.' This distinguishes it from sibling tools like 'get_schedule_v3_custom_shift' (singular) and 'list_schedule_v3_overrides' (overrides vs custom shifts).

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 for listing custom shifts but does not explicitly state when to use this tool vs alternatives like 'list_schedule_v3_overrides' or 'list_schedule_v3_rotation_events.' No exclusions or when-not-to-use guidance is provided.

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