claim_market_bounty

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

Describes the verification process, payout of full escrow with no rake, and refund to creator if unclaimed. No annotations present, so the description carries the burden; it covers success and expiry, but not 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?

Description is a single but informative sentence with no fluff. It packs verification criteria, payout, and expiry into a compact form, though it could be split for readability.

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 purpose, eligibility, payout, and expiry. No output schema exists, so no need to explain return values. Sufficient for an agent to understand when and how to use the tool.

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 descriptions already cover both parameters (api_key and order_id) with 100% coverage. Description adds no extra parameter-specific details, 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?

States a specific verb 'claim' and resource 'open bounty', and clearly explains verification against game records. Distinguishes from other market tools like buy/cancel/create by focusing on claiming bounties.

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?

Implies when to use by describing eligibility criteria (strike or war_participation bounties) and urgency (claim promptly). Does not explicitly list alternatives, but gives enough context to infer appropriate use.

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