extend_reservation

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

Explicitly discloses that 'THIS CHANGES STATE on TechZone', which is a critical behavioral trait. It also documents all possible return outcomes (extended, not_extendable, rejected, ambiguous) with explanations of what each means. Despite no annotations present, the description fully carries the transparency burden with actionable detail.

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?

Compact, front-loaded with the primary action in the first clause. The human-confirmation warning is prominent. The outcome enumeration is useful but slightly verbose; could be trimmed slightly. Overall well-structured and every sentence carries weight.

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?

For a state-changing mutation tool with no annotations and no schema descriptions, this is highly complete. It covers the return contract via output schema/outcomes, explains side effects (state change), warns about destructive behavior, and describes each possible outcome including the 'ambiguous' edge case. Excellent coverage.

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% and there are only 2 params. The description adds meaning for 'days' (defaults to 1, extends 'past its current provisionUntil'). reservation_id is self-explanatory as a string identifier. Description doesn't describe format/validation for reservation_id, but the behavior of each param is reasonably covered.

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+action: 'Extend a TechZone reservation's end date by N days' clearly states what it does. Distinguishes from siblings (get_reservation, cancel_reservation, create_reservation) by the specific action of extending end dates.

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?

Explicitly states when to use (extend reservation) and provides clear behavioral guidance - ALWAYS confirm with user before calling, specifying what to confirm (reservation name + days). This is a strong usage directive that goes beyond typical tool descriptions.

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