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

Annotations already establish this as a safe read, but the description adds substantial non-obvious behavior: it cannot charge or retrieve purchases, no keys should be sent, free evidence needs no payment, existing subscriptions exclude the four standalone licences, and compatible agents need owner spending authority. That is meaningful disclosure well beyond the structured hints.

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 purpose is front-loaded, but the middle sentences pack a lot of pricing and contract minutiae (GBP49, GBP79, agent_payments_contract, recovery) into one dense block. Much of this is useful, but the single-breath length reduces scannability.

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 input parameters and no output schema, the description compensates reasonably by enumerating what the response contains (availability, prices ex-VAT, requirements, contracts). An agent has enough to call it and interpret the result, though return-value specifics remain prose-only.

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?

There are zero parameters, so the baseline is 4. The description correctly signals the empty call ('Call with {}') and does not invent faux parameter semantics, which is appropriate.

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 the resource precisely (access and licensing options: paid saved retrieval, unsigned receipts, executable licences) and what it returns (live availability, GBP prices, product requirements, payment contracts). It is distinguishable from the free-preview sibling, though it lacks a crisp single verb and leans on enumerating return contents.

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?

Explicitly says to call it 'after a free preview' and points to purchase_url for hosted checkout, giving a clear sequencing condition and routing to a follow-up action. It stops short of naming sibling tools outright, so it is clear context rather than full when/when-not guidance.

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