get_upcoming_deadlines

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are filtered to 'confirmed' and 'actionable' deadlines and evaluated per purchase's timezone. It stops short of explaining how 'actionable' is determined or any rate/limit context.

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?

One tight sentence with no filler, and the core action is front-loaded. The trailing timezone clause is slightly compressed and could read ambiguously, but nothing is wasted.

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?

An output schema exists, so return values need not be described, and annotations cover safety. Still, for a tool whose central term is 'actionable confirmed', the description leaves that qualifier undefined and gives no routing guidance against the seven sibling tools.

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 coverage is 0% — the single 'days' parameter has only default/min/max and no prose. The description partially compensates by tying the window to 'within N days', but it never clarifies whether the window is calendar days from now, how the upper bound (3650) behaves, or what happens at days=0.

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 names a specific verb+resource ('Get ... deadlines') and adds scoping qualifiers ('actionable confirmed', 'within N days', 'in each purchase's timezone') that separate it from warranty or return-request siblings. It is clear what is retrieved, though it never explicitly contrasts itself with the other deadline-adjacent tools.

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?

Usage is only implied by the phrase 'actionable confirmed deadlines'; there is no explicit statement of when to call this versus get_warranty_status or generate_return_request, and no prerequisites or exclusions are given.

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