account_retrieve

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

With no annotations provided, the description carries the behavioral burden. The verb 'Get' implies a non-mutating read operation, and the scope of the account is clarified as the one owning the API key. However, it does not disclose things like authentication expectations, whether the call consumes credits, or response/error behavior; the simple nature of the operation keeps this from being more critical.

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, well-structured sentence conveys the purpose, the resource, and the scope of the account. There is no filler or repetition; every part of the sentence contributes meaning.

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 retrieval tool with an output schema present, the description is sufficient. It clearly states what is returned (credit balance and subscription details) and whose data is accessed (the API key owner). The output schema can handle the specific return structure, so no additional detail is required.

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, so the input schema is trivially complete and the description does not need to explain parameter behavior. The description still adds value by explaining what the returned data represents, which is more than the empty schema provides.

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 uses the specific verb 'Get' and names a precise resource: the current credit balance and subscription details of the API key owner's account. This clearly distinguishes it from the sibling tools, none of which target account or billing information.

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 gives clear context for when to use the tool: whenever an agent needs the account's credit balance or subscription details. It does not explicitly list when-not-to-use or name alternatives, but no sibling tool serves this purpose, so the usage context is strong.

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