Get RIPE Atlas Credit Balance

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

Annotations already indicate read-only and idempotent behavior. The description adds useful context: return fields (balance, income/expenditure, runout) and the prerequisite API key, which enriches the agent's understanding.

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 brief and efficiently lists arguments, returns, and requirements. It is front-loaded with the main purpose. Could be slightly more structured but is adequate.

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 simple balance check with one optional parameter, the description covers the purpose, argument, return values, and a prerequisite. No output schema exists, so the return description helps. It is sufficiently complete.

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 single parameter is fully documented in the schema with description and enum. The description repeats the same info without adding new meaning, so it does not go beyond what the 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 clearly states 'Check your RIPE Atlas credit balance and usage statistics', specifying the verb (check) and resource (credit balance/usage). It distinguishes from sibling tools which focus on measurements and probes.

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 notes the required environment variable and mentions the return values, but does not explicitly state when to prefer this tool over alternatives. However, the context makes the purpose clear enough.

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