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

The annotations already indicate read-only, idempotent behavior, so the description does not need to repeatedly state safety. It adds meaningful context by noting the operation is scoped to the authenticated account and that both balance and usage limits are included, which goes beyond what the annotations convey.

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, focused sentence that states the core behavior without any filler. It is appropriately front-loaded and easy for an agent to parse quickly.

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 zero-parameter, read-only, idempotent tool with an output schema, the description is complete. It identifies the subject (authenticated AlpineLead account) and the returned information (credit balance and usage limits), leaving no missing inputs or side-effect ambiguity.

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?

The tool has zero parameters in the input schema, so parameter documentation is not needed. The description adds no parameter-specific detail because there are none to document, matching the baseline expected for a no-parameter tool.

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 identifies the operation (returns), the resource (the authenticated AlpineLead account's credit balance), and extends the title with 'usage limits,' providing precise scope. It naturally distinguishes itself from sibling tools like get_credit_packs or create_credit_checkout, which are about purchasing or listing credit products rather than reading account state.

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 intended use is clear: call this tool when you need the current account-level credit balance and usage limits. It does not explicitly name alternatives or exclusions, but the authenticated account-specific framing makes the usage context obvious.

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