get_credits

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

Without annotations, the description only states 'Get current credit balance'. It does not disclose whether the operation is read-only or any side effects, rate limits, or authentication requirements. For a simple read, more context would be helpful.

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, concise sentence that effectively communicates the tool's purpose with no verbosity or irrelevant 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?

Given the tool's simplicity (no parameters, no output schema), the description is functional but lacks completeness. It does not specify the return type (e.g., integer, string with units) or whether the balance is real-time or cached.

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 input schema has no parameters, so schema coverage is 100%. The description adds no extra meaning beyond the schema. Baseline 3 is appropriate as the description is adequate but does not elaborate on the balance format or return details.

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 'Get current credit balance' clearly specifies the verb and resource. It is distinct from sibling tools like 'get_account_info' or 'get_usage', which cover broader or different data.

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?

No guidance is provided on when to use this tool versus alternatives. For instance, it does not indicate whether this is preferable to 'get_account_info' for credit-only queries or when to call it (e.g., before a purchase).

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