upcoming_shifts

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

With no annotations, the description carries full burden but only says 'list shifts'. It does not disclose important behaviors such as time zone handling, inclusion of current shift, sorting order, pagination, or data freshness. The output schema partially covers return structure, but behavioral traits are missing.

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?

A single sentence is appropriately concise for a simple tool. However, it could be slightly expanded to include parameter hints without losing brevity.

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 output schema exists, return values are covered externally. But the description lacks detail on time window behavior, time zone, and the calendar parameter. It is minimally complete but leaves gaps for an agent to infer correctly.

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 description coverage is 0%, so description must explain parameters. It implicitly covers 'days' via 'next number of days', but the 'calendar' parameter is not mentioned at all. Meaning is added for only one of two parameters.

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?

Description clearly states verb 'list', resource 'shifts', and time scope 'from now through the next number of days'. This distinguishes it from sibling tools like 'list_shifts' (all shifts) or 'shifts_on_date' (specific date). However, it could explicitly reference the 'days' parameter for extra clarity.

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?

No guidance is provided on when to use this tool versus alternatives like 'list_shifts', 'shifts_on_date', or 'current_shift'. The description only states what the tool does without contextual usage directives.

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