get_credits

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

No annotations provided, so description carries full burden. It specifies 'current' data (temporal context) but fails to disclose if this is cached/real-time, whether the operation is safe/read-only, or what format/structure the response takes given no output schema exists.

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?

Single 10-word sentence with no waste. Front-loaded action verb followed by specific data targets. Every word earns its place.

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?

Adequate for a zero-parameter read operation, but with no output schema and no annotations, the description should ideally sketch the return structure (objects, currencies, numeric formats) or mention this retrieves aggregated account data versus per-agent data.

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?

Zero parameters present, which establishes baseline 4. Description correctly implies no inputs are needed to retrieve account-level credit data.

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?

Clear verb 'Get' and specific resources (credit balance, monthly spending cap, usage) are listed. Implicitly distinguishes from sibling agent/product tools by addressing account billing data, though lacks explicit contrast with other 'get_' siblings like get_activity or get_dashboard.

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 provided on when to invoke versus alternatives (e.g., get_dashboard which might also show usage metrics), nor any prerequisites or conditions mentioned.

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