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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with an explicit statement that badges cannot be added or removed through this tool. It also lists the concrete fields in each ledger entry, though it says nothing about ordering, default time window, or total counts.

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?

One dense, front-loaded paragraph: resource and ledger contents first, then usage scenarios, then the read-only constraint. The parenthetical field list is information-dense rather than padded, though the sentence runs long.

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 describing return values, and it does so by enumerating the ledger fields. Combined with the filterable parameters and the read-only guarantee, an agent has everything needed to call it correctly.

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 limit, offset, and source are fully documented in the schema and the baseline is 3. The description's mention of source values (campaign check-in) loosely aligns with the source filter's example but adds no new filtering semantics.

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 (view badge balance plus issuance/consumption ledger) and enumerates the record fields returned: time, delta, resulting balance, source, and operation type. No sibling tool touches badges, and the description makes that scope unambiguous.

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?

Gives the concrete user questions that select this tool ("how did I get my badges", "have I had badges deducted recently"), which is a clear when-to-use signal. It does not name alternatives, but no sibling is a plausible substitute, so the gap is minor.

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