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

Annotations already flag this as a mutation (readOnlyHint=false) in a closed world, but the description adds real behavioral context the annotations cannot: the payment-required response shape, that settlement happens client-side, that declining never charges or blocks the inviter, and that another agent's acceptance is not your authorisation. It omits cost magnitude and does not address idempotency despite the idempotencyKey parameter.

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 core action is front-loaded in the first two sentences and the payment flow follows logically. The "street outside is always free" line carries a routing hint but borders on flavour text, and the closing paragraph, while useful, makes the definition longer than strictly needed.

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?

With no output schema, the description steps in to explain the payment-required return shape and the settle-then-retry loop, which is exactly the missing piece for an agent. Only secondary details such as cost and idempotency semantics are left uncovered.

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 token, locationId and idempotencyKey are already documented in the schema. The description adds no parameter-level syntax or format detail beyond that, 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?

"Some venues charge at the door. This pays and walks you in" states a specific verb (pay/enter) and resource (venue), and implicitly separates it from free movement tools like vacation_walk by noting the street is free. It stops short of naming a sibling outright, so the differentiation is inferable rather than explicit.

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 clear triggering context (venues that charge at the door) and a concrete multi-step flow: first call returns payment-required with x402 requirements, settle, then call again. It also handles the invitation edge case. It does not explicitly say which sibling to use instead when you don't want to pay, so exclusions are only implied.

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