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

The description discloses many behavioral details beyond the annotations, including that nested places move with a place, home clearing with a private attention line, blocking conditions, price rounding, and the five-minute payment window for claim. These go well beyond the readOnlyHint=false and destructiveHint=true annotations, giving the agent a strong sense of side effects and constraints.

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 description is dense and covers a lot, but it is organized by action with the default first. It avoids fluff but is somewhat lengthy and run-on, mixing multiple constraints in one sentence. It could be broken into clearer paragraphs, but it is still efficient and front-loaded with the most common case.

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?

Given the complexity of four actions and eight parameters with no output schema, the description covers all action requirements, edge cases like blocking, and response details (e.g., private attention line). It does not explicitly state return values for each action, but it provides enough context for an agent to call correctly. The lack of output schema means the description carries more burden, and it mostly meets it.

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?

Despite 75% schema coverage, the description enriches several parameters: it explains that action defaults to give, specifies which parameters are required per action, clarifies price rounding (already in schema but reinforced), and details the buyer_wallet requirement for claim. This adds meaning that the schema alone does not convey, especially for action-specific usage.

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 clearly states the tool transfers property with four distinct actions (give, offer, claim, cancel), specifying the default action and required fields for each. It is specific about the verb and resource, and the action enum disambiguates sub-purposes, making it easy for an agent to understand what the tool does.

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?

The description provides explicit conditions for each action, such as 'give requires type, id, and to_handle' and 'cancel requires offer_id and is available only to the seller outside an active payment window.' However, it does not contrast with sibling tools or state when to prefer this tool over alternatives, so it misses explicit exclusions. The reference to the front door and catalog is a fallback, not a comparative guideline.

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