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

No annotations so description bears full burden. The verb 'Get' implies read-only, but no explicit statement about side effects, required permissions, error handling, or rate limits. Provides minimal behavioral context beyond the obvious.

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 efficient sentences, front-loaded with purpose. No redundant or extraneous information.

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?

The tool is simple but has no output schema. The description gives a general idea of return content (balance, ledger) but lacks specific format, structure, or pagination details. Adequate but could be more precise.

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 covers 100% of the single parameter with 'boom_sk_ key.' description. The tool's description only says 'Requires a key,' adding no new meaning beyond the schema. Baseline of 3 is appropriate.

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 clearly states the tool retrieves a prepaid credit balance and recent ledger for a given key, specifying currency and ledger contents. It distinguishes from sibling tools like buy_credits or list_topup_packs.

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 implies when to use (checking balance/ledger) but does not explicitly state when not to use or provide alternatives. It lacks guidance on preferring other tools for related operations.

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