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

Annotations already declare this is a non-destructive, non-read-only, idempotent, closed-world mutation, so the bar is lower. The description adds genuinely useful behavior beyond that: a 72-hour hold window, zero cost ('Free'), the re-claim refresh semantics, the explicit fact that the agent never posts, and the 409 conflict meaning. Minor residual tension: 'Claiming again refreshes the hold' is a repeated-call side effect on the hold expiry, which sits slightly awkwardly beside idempotentHint=true.

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?

Front-loads the core action and its constraint (72-hour hold, no competing replies) before the price, the workflow routing, and the error case. Every sentence carries operational information; none is restatement of the name or title.

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?

There is no output schema, but the description compensates by enumerating the return payload (post link, drafted opener, scout's links) and the full downstream workflow. Combined with annotations covering safety, an agent has everything needed to call this correctly and act on the result.

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 100% and the single dealId parameter is fully documented in the schema as coming from get_scout_deals, so the baseline of 3 applies. The description adds indirect context (the deal belongs to 'this scout' and re-claiming targets the same deal) but no new syntax or format detail.

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 and resource ('Hold a deal for this scout for 72 hours') and immediately clarifies the effect on other scouts replying to the same founder. It is clearly distinguishable from siblings like release_deal, report_deal_progress, and get_scout_deals, which are either named in the workflow or implied by contrast.

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?

Gives explicit timing ('Call it when the user decides to reply, BEFORE they post') and routes the agent to the follow-up tool with the exact argument ('report_deal_progress with stage 'sent' and the reply URL'). It also covers the failure path: '409 claimed_by_another_scout = someone else holds it; pick another deal.'

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