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

With no annotations, the description carries the full burden and does well: it discloses that the call is billable (£0.49), that it returns a Stripe Checkout URL rather than amenity data, that the data is OSM/ODbL with attribution obligations, and that 'Soft-Offer outbound is OFF'. It omits auth requirements, rate limits, and what the caller should do after payment completes.

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?

Three short sentences, front-loaded with the purpose and cost, no filler. 'Soft-Offer outbound is OFF' is unexplained internal jargon, which costs it a point, but everything else earns its place.

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?

No output schema exists, and the description compensates by naming the exact return artifact (Stripe Checkout URL), which is the single most important thing an agent needs to know. The remaining gap is the workflow tail — nothing points to redeem_pack as the follow-up after payment.

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 both parameters (postcode, size) are already documented, and the baseline is 3. The description reinforces the postcode/outcode input format but adds nothing about the 'size' parameter's default or max.

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?

States a specific resource ('pack of nearby UK amenities') with a concrete scope ('for a postcode/outcode') and adds the material fact that it is a paid pack. It does not explicitly name or contrast with the sibling local_amenities_discover, so the free-vs-paid distinction must be inferred from the word 'Paid'.

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?

There is no explicit when-to-use statement or exclusion; the only guidance is implicit via 'Paid' and the £0.49 price, which hints this is the purchase path rather than the discovery path. Nothing tells the agent to prefer local_amenities_discover when a free lookup suffices.

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