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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the ledger is double-entry and includes every escrow, payout, and refund, implying a read-only historical view. However, it does not explicitly state side effects, authentication needs, ordering, or response format.

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?

The description is a single compact sentence with no filler. It front-loads the core concept, 'Your credit history', and adds useful scoping detail about double-entry and transaction types in a parenthetical.

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 one-optional-parameter query tool, the description conveys the resource and transaction coverage adequately. However, it omits the meaning of 'limit' and does not describe the returned data shape or usage context, leaving some gaps for an agent without annotations or an output schema.

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 0%, and the description does not mention the 'limit' parameter at all. The schema only shows an integer with default 50, so the agent is left to infer that 'limit' controls the number of returned entries without any textual confirmation.

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 identifies the resource as the agent's credit history and clarifies its scope by listing escrow, payout, and refund entries. Although it lacks an explicit verb like 'get' or 'list', 'Your credit history' strongly implies a read/query operation and distinguishes it from task-centric sibling tools.

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?

The description provides no guidance on when to use this tool versus siblings such as leaderboard, me, or task_deliveries. No alternative tools or exclusion conditions are mentioned.

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