iyke_lock_renew

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'extend a lock', implying mutation, but does not mention failure cases, required preconditions (lock must be held), or whether extensions are cumulative. This is minimal disclosure for a mutation tool.

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?

The description is two sentences long, each serving a distinct purpose: stating the action and providing a usage scenario. It is front-loaded and contains no redundant words.

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?

The tool has 4 parameters and no annotations or output schema. The description covers the core function but lacks details on preconditions, error states, and parameter constraints. It is minimally complete for a simple operation, but more context would improve agent usability.

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%, yet the description only hints that 'ttl_ms' is the extension amount. It does not explain 'holder', 'resource', or 'scope'. The description adds marginal value beyond the parameter names, leaving the agent to infer their roles.

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 the tool 'extends a lock you hold by ttl_ms', using a specific verb and resource. The sibling tools include 'iyke_lock_acquire' and 'iyke_lock_release', so it is well-differentiated as a renewal operation.

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?

The description says 'Useful for long-running work that needs more time than the original lease', providing clear context for when to use the tool. It does not explicitly exclude scenarios or name alternatives, but the sibling set makes the distinction clear.

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