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

Beyond the annotations (destructive, open-world, non-idempotent) the description discloses the crucial trait that the intent does NOT reserve the item, that the first city reservation wins, the ten-minute expiry window, and the one-active-checkout-per-market rule. These are exactly the non-obvious behaviors an agent needs before acting.

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?

Four sentences, front-loaded with the core action, then constraints and prerequisites in descending priority. Slightly verbose but every sentence earns its place; no 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 two-parameter mutation tool with no output schema, the description covers reservations, expiry, rate limits, and prerequisites well. It omits what the checkout intent returns and how it relates to the 'buy' sibling, which is the main 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?

Schema coverage is 50%: city_handle carries a regex description while listing_id is undocumented in both places. The description does not add meaning for either parameter, only implying that city_handle is tied to the resident identity. Baseline 3 is appropriate given partial schema coverage and no compensating 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?

The description gives a specific verb+resource ('Create a ... checkout intent') and names the key properties (public, ten-minute, tied to an existing city resident). It does not, however, differentiate itself from the sibling 'buy', which an agent will likely weigh against this tool before acting.

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?

Clear prerequisites are stated: you must be a city resident, and if not you must register and pick a name first. It also states the one-active-checkout-per-buyer-and-listing rule and the ten-minute wait before another. The gap is that it never says when to use checkout_world versus the sibling 'buy' tool.

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