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

With no annotations, the description carries the full burden and does real work: it discloses the paid nature (£0.49), the exact return artifact (a Stripe Checkout URL rather than the data itself), the mandatory follow-up redemption step, and a compliance posture ('Soft-Offer outbound is OFF'). It omits auth requirements, token expiry, and what happens if the purchase is abandoned.

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 what the tool produces and followed by the required next step. The final clause about Soft-Offer outbound is terse and slightly cryptic, but every sentence carries information and nothing is padded.

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 two-parameter purchase tool with no annotations and no output schema, the description covers the essentials: cost, return value (Checkout URL), and the redemption handoff. It does not explain what the delivered pack actually contains or how the one-time token is obtained, leaving a modest gap.

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 'area' and 'size' are already documented in the schema, including the default of 25 and max of 100. The description only reinforces that the pack matches 'an area', adding no format or syntax detail beyond the schema — 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?

The description names a concrete resource ('paid pack of newly incorporated UK companies') and its scoping ('matching an area'), which distinguishes it from new_cos_discover and kyb_pack on subject matter. It does not name those siblings explicitly, so an agent must infer the routing rather than being told it.

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?

Usage is implied through the workflow: buy the pack, then 'redeem with one-time token', which points at the sibling redeem_pack without naming it. There is no explicit statement of when to choose this over new_cos_discover (free discovery) or kyb_pack, and no prerequisites such as account or payment-method requirements.

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