lease_acquire

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

No annotations provided, but the description fully discloses behavior: exclusive lease, TTL-based, automatic expiry on crash, and return values (acquired=True with expiry timestamp, acquired=False with holder ID). This provides thorough transparency beyond structured data.

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?

Three concise sentences, front-loaded with the action, and structured with clear sections. No wasted words; 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 all necessary aspects: purpose, usage scenario, behavior, and outcomes. With an output schema present, return value explanation is sufficient. Complete for a tool with 3 parameters.

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%, so the description must add meaning. It implies the roles of resource_id, holder_id, and ttl_seconds through context ('named resource', 'holder', 'TTL-based'), but does not explicitly list or describe each parameter. Adequate but not explicit.

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?

Description clearly states the action: 'Try to acquire an exclusive, TTL-based lease on a named resource.' It uses a specific verb and resource, and distinguishes itself from sibling tools like lease_release and lease_renew.

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: 'Use this to prevent split-brain when multiple agents could simultaneously work on the same resource.' While it doesn't explicitly list when not to use, the context and sibling tools imply it's for acquiring, not releasing or renewing.

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