get_advertiser_balance_tool

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

Discloses the 'Max 100 IDs per request' constraint, implying read-only behavior, but lacks details on authentication, rate limits, or side effects. Without annotations, more behavioral context would be valuable.

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?

Two sentences, front-loaded with purpose and key constraint, no waste.

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?

Output schema exists so return format is covered, but missing input format details, error handling, and rate limits make it barely adequate for a simple tool.

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 0%, yet description only mentions 'Max 100 IDs per request' without explaining the 'advertiser_ids' parameter (e.g., format, source, or that they are unique identifiers).

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?

Description clearly states verb 'Get' and resource 'balance and basic info for individual advertiser accounts', but does not distinguish among sibling tools like get_bc_balance_tool or get_business_centers_tool.

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 on when to use this tool vs alternatives; only provides a limit of 100 IDs per request, which is a constraint but not contextual usage advice.

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