UK Flood Risk MCP

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.

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.

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

No annotations are provided, so the description carries the full disclosure burden. It says nothing about side effects (does it grant entitlements or credit a pack?), idempotency on repeated redemption, error behavior for unpaid/invalid sessions, or required auth, all of which are essential for an unreversible-sounding redemption operation.

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?

It is short, but brevity here comes from under-specification rather than efficiency; a single fragmentary sentence that reads like a heading and conveys almost nothing front-loaded.

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 mutation-style tool with zero annotations, no output schema, and an undocumented required parameter, the description provides none of the context needed to invoke it correctly or interpret the result.

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% and the single required parameter session_id is completely undocumented in the description. The agent gets no indication that the identifier is a Stripe Checkout session ID, what format it takes, or how to obtain it.

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 text reads as a title fragment ('How to redeem...') rather than a statement of what the tool does. It gestures at the resource (a paid Stripe Checkout session) but never says the tool actually performs the redemption or returns anything, leaving the verb ambiguous.

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?

Mentioning 'paid' implies this only applies to completed checkout sessions, which is a faint usage cue. But there is no explicit when-to-use, no prerequisites, and no reference to the sibling tools epc_pack or epc_discover, which are plausible alternatives an agent would need to disambiguate against.

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