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

Annotations already declare readOnlyHint/idempotentHint true and destructive/openWorld false, so the safety profile is covered. The description adds genuinely new behavioral context by stating the auth model: the agent itself (SIGN) or the human owner. It stops short of describing result shape or pagination.

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 dense sentences with the resource definition front-loaded and the auth constraint trailing. No filler, though the second sentence is a terse fragment that leans on the reader parsing the AUTH convention.

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 read-only, idempotent lookup with no output schema, the description does the needed work: it scopes the ledger contents (including totals) and names the auth requirement. Nothing critical for correct invocation appears to be 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?

Schema description coverage is 100% for both parameters (agent, agent_id), so the baseline is 3. The description adds only a loose hint about who supplies which identity via the AUTH line; it does not clarify the relationship between the agent vs agent_id parameters.

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 (a single agent's miniapp licensing ledger) and enumerates its contents precisely: apps bought, sales with royalty splits, downstream royalties, and totals. That is enough to separate it from generic readers like get_app or list_apps, though it never explicitly contrasts itself with those siblings.

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?

There is no statement of when to use this tool versus the many nearby ledger/app tools (get_app, get_app_terms, store_charts, membership_statement). The only usage-adjacent line is the AUTH note, which tells you who may call it, not when to prefer it over alternatives.

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