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

The description discloses substantial behavioral detail beyond the annotations: idempotent re-reads ('repeating this sync only rereads that review state'), a bounded lock window ('at most two hours of automatic city recovery'), and the full set of terminal outcomes (needs_review, payment_invalid, payment_expired, founder_review). These align with idempotentHint/destructiveHint/openWorldHint, and 'This never takes payment' clarifies the money-handling boundary.

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 a dense run-on that repeats 'do not pay again' three times and buries the core action under state-machine jargon. The key instruction (how to invoke and what sync does) is not front-loaded, and several sentences restate the same retry guidance.

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 stateful mutation tool with no output schema, the description does enumerate the terminal states and retry semantics, which is meaningful. But it leaves the required listing_id unexplained, does not describe what success writes back to the caller, and its city/market framing adds ambiguity rather than resolution.

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 0% for the single required parameter listing_id, and the description never explains or even mentions it. It mentions 'listing' concepts only implicitly, adding no meaning about format, range, or expected value. With low coverage the description should compensate, and it does not.

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 opening states a specific action ('read the city public offer and mirror a completed ownership transfer or cancellation into the market'), which is more than a restatement of the name. However, the 'city/market' duality is opaque jargon and the description never distinguishes this tool from close siblings like buy, checkout_world, cancel_world_draft, or world_status. An agent can roughly infer the purpose but not cleanly separate it from the purchase/cancel tools.

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?

Usage is implied rather than stated: the description tells the agent to 'retry this same sync' on unavailable finality and 'do not pay again', which implies it only follows a completed transfer or cancellation. But it never names an alternative tool or states explicitly when to call this versus buy or checkout_world. The guidance is behavioral narration rather than when-to-use routing.

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