get_account_balance

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds the behavioral trait of 'real-time' data retrieval, which is not captured by annotations. No contradictions found.

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 extremely concise: a single line stating the purpose and endpoint. While this is efficient, it could be structured more clearly, e.g., by separating the endpoint from the purpose. Still, it is front-loaded and avoids fluff.

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 (a read operation to retrieve balance) and the presence of an output schema, the description provides adequate context. It covers the essential 'what' and 'how' but omits details like rate limits or authentication requirements, which are less critical for a straightforward read.

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?

Schema coverage is 100%, and the input schema provides detailed descriptions for both parameters. The tool description does not add any additional meaning beyond what the schema already offers. Baseline score of 3 is appropriate.

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 the tool's purpose: getting the real-time balance of an advertising account. It includes the API endpoint, which provides additional specificity. This distinguishes it from sibling tools like 'get_account_performance' or 'get_ad_account'.

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 mentions 'real-time balance', but does not provide explicit guidance on when to use this tool versus alternatives or any conditions. It lacks when-not-to-use instructions, leaving the agent to infer from context.

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