claim_after_timeout

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

No annotations provided, so description carries full burden. It discloses that calling before timeout will fail on chain and mentions return value (confirmation or error). Could add more about state changes or side effects, but sufficient.

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?

Description is concise: purpose in first sentence, usage conditions, precondition, then Args/Returns. No unnecessary words, well-structured for quick parsing.

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?

Completeness is high given the simplicity: one required parameter, output schema exists, and description covers when/why/how to use, including failure condition. No gaps.

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?

Only one parameter (job_id) with type integer. Schema coverage is 0%, so description must add value. The description says 'The contract ID to claim from after timeout,' clarifying the schema's vague 'Job Id' tag. Adequate but minimal.

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 explicitly states the action: 'Claim funds as the worker after the review window expires without requester action.' It specifies the resource (funds), the subject (worker), and the condition (timeout), clearly distinguishing from siblings like claim_funds.

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 context: 'Use this for Mode B contracts in AwaitingApproval status where the requester has not approved or disputed within the review_window_blocks set at creation.' Also advises to check view_contract first and warns that calling before expiry will fail.

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