claim_card

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

Discloses atomic leasing, lease expiry, heartbeat renewal, owner override, and crash recovery. Adds significant value beyond annotations (readOnlyHint=false, destructiveHint=false).

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: purpose/atomicity, expiration/owner override, and usage convention. No fluff.

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 leasing timeout, renewal, owner override, and post-claim convention. Could mention failure mode if card already claimed, but output schema likely covers return values.

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?

With 0% schema description coverage, description compensates by explaining `owner` (override actor) and `ttl_seconds` (lease expiry). `card_id` is self-explanatory.

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?

Specific verb 'lease a card' and resource 'card' with clear atomicity guarantee. Distinguishes from siblings like heartbeat_claim and release_claim.

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?

Describes conventions (after claiming, assign yourself and move to started column) and expiration behavior. Lacks explicit when-not-to-use but provides sufficient context.

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