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

Annotations only say this is a non-read-only, open-world, non-destructive write. The description adds substantial behavior the annotations cannot convey: it does not transfer ownership by itself, a six-digit code goes to the contact on file (not the requester), the code entry completes the handover, places with no contact wait for Phorme's team, and no payment is taken.

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?

The trigger condition leads, then the mechanics, then constraints — a sensible order for an agent. It is a bit long, with several clipped sentences ('It takes no payment. It needs a connected Phorme account.'), but each carries distinct constraints rather than filler.

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?

For a multi-step, manually-verified claim flow, the description covers eligibility, the consent gate, the out-of-band code path, the no-contact fallback, cost, and account requirements. An output schema exists, so return values need not be explained.

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%, so place_id, via, and confirmation are already documented including the enum default and the const:true constraint. The description reinforces confirmation's intent but adds no syntax, format, or edge-case detail beyond what the schema provides, so the baseline 3 applies.

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 states a specific verb and resource (claim a place) and pins down the exact situation: a place Phorme already lists that nobody runs on Phorme. That condition implicitly separates it from create_or_claim_place (unlisted places) without naming the sibling, which is a minor gap but the scope is unambiguous.

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?

It gives an explicit trigger with a quoted owner utterance ("that gym is mine"), states the prerequisite (connected Phorme account) and the operational instruction to confirm with the owner before setting confirmation=true. Nothing about when to use it is left to inference.

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