get_balance

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds behavioral details such as 'no side effects,' response fields (mode, auto_reload, URL), and hints for enabling auto_reload, going beyond annotations.

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 moderately sized but each sentence adds distinct value: purpose, usage, read-only nature, response details, disambiguation. It is well-structured and front-loaded, though slightly verbose in the disambiguation part.

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 zero parameters, 100% schema coverage, and an output schema, the description is fully complete. It covers what the tool does, when to use, the response structure, and how it differs from siblings.

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?

No parameters exist, so baseline is 4. The description does not need to add parameter info, and it sufficiently explains the output, which is the only relevant aspect.

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 'Check the prepaid balance' and specifies the resource (balance in cents) and its purpose (fund submit_query calls). It also disambiguates from sibling tools by noting it does not list queries or responses.

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?

Explicitly advises when to use: 'Call before submit_query if unsure funds suffice, or whenever a query fails/stalls for balance reasons.' Also mentions it's free in test and live mode, providing clear contextual guidance.

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