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

With no annotations, the description carries the full burden. It discloses the cost (£0.49), that it returns a Stripe Checkout URL, and the cryptic 'Soft-Offer outbound is OFF'. However, it does not explain whether payment is immediate, whether data is returned before or after checkout, or what side effects occur.

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 short and front-loads the key facts (paid, output type, cost, data domain). The final sentence 'Soft-Offer outbound is OFF' is unexplained jargon but does not bloat the text significantly.

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 no annotations, no output schema, and 0% parameter description coverage, the description is incomplete. It leaves out 'size' semantics, payment flow details, and sibling differentiation, which are important for a paid tool.

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%. The description mentions 'postcode' but adds no format or usage detail, and the 'size' parameter is completely unexplained. It compensates only marginally for the lack of schema documentation.

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 states a specific output (Stripe Checkout URL for £0.49) and data domain (England flood warnings, flood areas, river stations for a postcode). It does not explicitly differentiate from the sibling flood_discover, leaving some ambiguity about its precise role.

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 guidance on when to use this tool versus flood_discover or redeem_pack. 'Paid pack' implies a purchase context but does not specify prerequisites, alternatives, or when-not-to-use.

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