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

Annotations already cover read-only/idempotent/non-destructive, so the description goes beyond them by disclosing the crucial empty-result semantics tied to the `coverage` field ('empty list means none are indexed in the period the coverage field names, not that none happened before it') and that each event carries its transaction. Missing ordering/pagination context keeps it from a 5.

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?

Front-loaded with the core purpose, but the single dense paragraph mixes taxonomy, filtering, and a caveat, making it somewhat heavy to parse. Every sentence is substantive, though, so little waste.

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 output schema, the description carries the burden of return values and does so reasonably: events are returned per transaction and include a `coverage` field bounding the indexed period. It omits result ordering and pagination behavior, which an agent might want.

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 the enum and parameter meanings are already documented in structured form; the description's prose mapping of freeze/unfreeze/third_party largely repeats the enum description. It adds only light value, such as framing `credential` as the wallet 'frozen, taken from, or given tokens'.

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?

Starts with a specific verb and resource ('What issuers of programmable tokens (CIP-113) have done, each with its transaction'), then enumerates the event classes (freeze, unfreeze, third_party, mints/burns, state_changed, etc.). This clearly distinguishes it from siblings like get_programmable_balances (balances) and get_programmable_token (token metadata).

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?

States the filtering axes ('Filter by token, by kind or by the wallet credential concerned'), which tells the agent how to scope the query. It does not explicitly name a sibling alternative or an exclusion ('use X instead'), so it stops short of the top score.

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