check_expiring

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

No annotations are provided, so the description carries the burden. It discloses the default window behavior and exclusion criteria, which is useful. However, it doesn't add much beyond the obvious read-only nature implied by 'flag'/list semantics, and doesn't detail the output shape beyond hoursRemaining. 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?

Three concise sentences, each earning its place: what it does, the default behavior, the use case, and the exclusion. Zero waste and front-loaded with the core action.

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?

Has an output schema (which explains return values), a single simple parameter, and no annotations needed for a read-only flagging tool. The description covers the window, ordering, countdown field, and exclusions. Reasonably complete given the low complexity; could mention whether it requires prior list context, but that's minor.

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%, so the description must compensate for the single 'days' parameter. It does explain the parameter's effect ('within the next N days, default 3'), which covers what matters. Description fully compensates for the coverage gap on this simple parameter.

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?

Specific verb+resource: 'Flag active reservations ending within the next N days.' Clearly distinguishes from siblings like list_reservations and get_reservation by its time-based expiry focus, and states the output ordering (soonest first) and countdown field (hoursRemaining).

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?

Gives an explicit use-case question ('is anything about to expire?') and explicitly states what's excluded (deleted/expired reservations). It doesn't name a specific alternative tool for the when-not case, but the positive use-case is clear enough to guide selection.

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