Renew file reservation

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

Discloses side effects ('updates reservation expiry and audit rows') and failure modes ('returns zero when no matching active reservation exists'). No annotations provided, so description carries full burden; it is sufficiently transparent.

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?

Well-structured with headings (Purpose, When to use, Inputs, etc.). No fluff, every sentence adds necessary information.

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?

Covers purpose, usage, side effects, output, and failure modes. Output schema exists, so return details are not needed; description is complete for a renewal tool with 5 params.

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 100%, baseline 3. Description adds value by summarizing input combinations ('workspace_id plus reservation_id or file_path'), which aids correct usage beyond schema descriptions.

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 'Extend active file reservations while work continues,' which is a specific verb+resource. It distinguishes from sibling tools like reserve_files (creates) and renew_symbol_reservation (symbol-specific).

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 says 'When to use: call before TTL expiry if an agent still owns the edit.' Provides failure mode context but does not explicitly list when not to use or name alternatives.

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