extend_signal_lease

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

With no annotations, the description adds some behavioral context: expired leases can't extend, hard expiry takes precedence. However, it partly restates schema parameter descriptions (e.g., lease_seconds extending from current end). Missing details like side effects, auth requirements, or error cases.

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?

Four concise sentences with the core action in the first sentence. No redundant information; every sentence adds value.

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 prerequisites (active lease, consumer ownership), constraints (expired, hard expiry), and usage scenario. With an output schema present, return values need not be described. Lacks information about rate limits or potential errors, but adequate for the complexity.

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% with detailed parameter descriptions. The description does not add additional meaning beyond the schema, so baseline 3 is appropriate.

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 identifies the action (extend) and the resource (active lease on a claimed signal). It distinguishes from siblings like claim_signal by focusing on extending an existing lease rather than acquiring a new one.

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 ('when a worker still owns a signal but needs more time') and when not to ('expired leases cannot be extended; must be reclaimed'). Mentions hard expiry precedence. Could be improved by explicitly naming sibling alternatives like 'claim_signal' for new leases.

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