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

Annotations only declare the generic safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true); the description goes well beyond them. It discloses side effects ('its nested places move with it,' 'your home is cleared'), blocking conditions ('a nested place with another owner or an open sale blocks the whole gift'), the muted-recipient waiting flow, the five-minute payment reservation, and the re-validation on accept.

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 text is long but dense, and each sentence carries a distinct rule rather than filler. It is organized action-by-action, though the ordering is implied rather than signposted and the cryptic closing aside ('Lost? Call front_door') is the only sentence with low information value.

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 nine-parameter, output-schema-less multi-action tool, the description does substantial lifting: it names response fields (waiting_transfers, the attention line) so the agent knows what comes back, and covers blocking and timing behavior. It stops short of spelling out the full result shape per action, which would be the remaining gap.

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 78% schema coverage the schema already documents most parameters, so the baseline is 3; the description adds conditional meaning the schema can't express, such as which parameters each action requires and the buyer_wallet reservation role. It does not add much beyond the schema for id/type on the give path, but the action-to-parameter mapping is genuinely additive.

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 enumerates the six concrete operations (give, offer, claim, cancel, accept, decline) and the resources they apply to (place, thing, kind), so the transaction semantics are clear. What it lacks is a single front-loaded statement of the tool's overall purpose — it opens mid-rule with 'Omitting action defaults to give,' relying on the reader to infer 'transfers ownership.'

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?

Each action is routed with explicit prerequisites and exclusions: 'give requires type, id, and to_handle,' 'claim requires offer_id; its first call also requires buyer_wallet,' and 'cancel ... is available only to the seller outside an active payment window.' It also supplies a fallback ('Lost? Call front_door'), leaving no ambiguity about which action to pick or when.

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