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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely useful business context beyond that: the cashback is paid by SPI to the client and never to an agent, SPIs confirms the contract, no lead is created and no payment is initiated — all of which prevent an agent from misrepresenting side effects.

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?

Content is front-loaded: what is read and which fields, then the payment/no-side-effect disclaimers. The second sentence carries some defensive repetition about agents never being paid, but that clause earns its place by heading off a plausible misreading.

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 an output schema present, the description need not document return values, yet it helpfully names the fields anyway. Combined with full annotation coverage and zero parameters, an agent has everything needed to call it correctly; only explicit usage guidance is absent.

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?

The tool takes zero parameters, so the baseline is 4; no parameter explanation is needed or missing. The description correctly implies a parameterless, fetch-the-singleton-programme call.

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?

States a specific verb and resource ('Read the published cashback programme of Swiss Premium Insurance') and enumerates the exact contents returned (status, version, payer, beneficiary, trigger, conditions, terms links), so an agent knows precisely what it will get. None of the sibling tools touch cashback, so differentiation is implicit rather than stated.

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 only implied by the resource itself; there is no explicit statement of when to call this versus an alternative, and no prerequisites or exclusions are given. In fairness, no sibling tool overlaps with this domain, so there is little routing ambiguity to resolve.

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