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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that results are paginated and scoped to the current identity, but says nothing about ordering, result window, rate limits, or auth requirements. For a read-only listing tool this is passable but thin.

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?

A single front-loaded sentence with no filler; the resource and scope come immediately. It is efficient, though arguably it could spend another clause on the sibling distinction without becoming bloated.

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 simple read-only listing tool with no output schema, the description covers the basics but omits what a usage entry contains and how this differs from codebase_get_credits. With two parameters undocumented and no annotations, the definition is minimally viable rather than complete.

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 coverage is 0% with two undocumented parameters (limit, offset). The word 'paginated' hints that pagination parameters exist, but the description does not explain the offset/limit semantics, the maximum of 200, ordering, or defaults, so it fails to compensate for the coverage gap.

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 states a clear verb ('Read') and resource ('credit usage history') with an explicit scope ('for the current identity'), so an agent knows what it returns. However, it never differentiates itself from the obvious sibling codebase_get_credits, leaving ambiguity about which credit-related tool to pick.

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 guidance about when to use this tool versus codebase_get_credits, nor any mention of prerequisites or context. The agent must infer usage purely from the name, which is risky given two credit-related siblings.

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