extend_signal_lease

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 that expired leases cannot be extended and that hard expiry overrides lease renewal. It does not detail error states or idempotency, but the key behaviors are covered.

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 concise with two short paragraphs. The first sentence immediately states the purpose, and the second paragraph adds usage guidelines. No extraneous 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?

Given no annotations and an output schema (not shown but present), the description provides sufficient context for a lease extension tool. It explains the core behavior, constraints, and relates to sibling tools implicitly. Minor gap: no mention of return value or error handling.

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%. The description adds meaning beyond schema: 'id' is exact signal id, 'consumer' is current claimant, 'lease_seconds' extends from current lease end but not beyond hard expiry. This provides critical context for correct invocation.

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's purpose: extending the active lease on a claimed signal. It uses a specific verb ('extend') and resource ('active lease on one claimed signal'), and distinguishes from sibling tools like 'claim_signal' and 'ack_signal'.

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?

Provides explicit guidance on when to use (worker owns signal, needs more time) and when not to use (expired leases must be reclaimed). Mentions precedence of hard signal expiry, clarifying boundary conditions.

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