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

Annotations already declare read-only, idempotent, non-destructive, and non-open-world, so the safety profile is covered. The description adds genuinely new context beyond those hints: the call is free (no credit spend), requires no bearer token, and does not inspect any transaction. Auth and cost behavior are exactly the traits annotations cannot express.

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?

Two tightly written sentences with no filler: the purpose and price lead, the coverage list follows, and the exclusions close. Every clause carries information an agent would otherwise have to guess.

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?

An output schema exists, so return values need not be described; what the agent does need — what topics the info covers, that it is free, that no token is needed, and that it is not a transaction lookup — is all present. Nothing required for correct invocation is missing.

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 there is no parameter semantics to document and the baseline is 4. With 100% schema coverage and an empty input object, nothing is left ambiguous.

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 specific resource (the Base Payment Assurance service) and frames it as a free overview, plus enumerates the concrete facts it exposes (chain/token, dual-RPC quorum, safe-finality, exact-transfer policy, fail-closed behavior, credit cost). It clearly separates itself from transaction-inspecting siblings via negation, though it does not name an alternative directly.

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?

It states an explicit use case ('Use this to learn...') and sets boundaries ('does not inspect a transaction and does not require a bearer token'), which tells the agent when this tool is and is not appropriate. It lacks an explicit routing statement naming a sibling for the transaction-inspection case, so it stops short of a 5.

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