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

With no annotations, the description must carry the full behavioral burden. It discloses a maximum result cap of 5 and an England-only scope, but omits authentication needs, rate limits, error behavior, and return format. The trailing 'Soft-Offer outbound is OFF' is opaque and adds little actionable clarity.

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 very short and front-loads the result cap and geographic scope. However, the closing 'Soft-Offer outbound is OFF' is unclear jargon that weakens the structure rather than adding useful context.

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 annotations, no output schema, and one of two parameters undocumented in the schema, the description should provide more operational detail. It states scope and a cap but leaves return values, permissions, and error handling entirely unspecified.

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%: postcode has an example ('SW1'), but size is undocumented. The description's 'max 5' partially compensates by implying size is capped at five, though what size represents (e.g. result count) remains implicit.

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 identifies the resource and scope: England flood warnings, flood areas and river stations for a postcode, plus a 'free peek, max 5' limit. However, it uses no clear verb and does not explicitly differentiate itself from siblings flood_pack or redeem_pack, leaving the action somewhat vague.

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?

The phrase 'Free peek, max 5' hints at a preview use case, but there is no explicit guidance on when to use this tool versus flood_pack or redeem_pack, nor any when-not conditions or prerequisites.

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