get_advertiser_balance_tool

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

With no annotations, the description carries the burden of behavioral disclosure. It does state that it returns advertiser_id, balance, credit_limit, and currency for each account, which clarifies the outcome. However, it does not mention read-only behavior, authentication requirements, pagination, possible empty results, or error cases, leaving some behavioral gaps.

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 three short, purposeful sentences with no filler. It leads with the tool's purpose, then the return values, then the prerequisite. Every sentence 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?

For a one-parameter getter with an output schema, the description covers the essential context: what it returns é and how to get the required bc_id. It lacks explicit notes on access restrictions or empty results, but those are not critical for this simple read-oriented 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%, so the description must compensate. It successfully ties the lone parameter bc_id to a Business Center and tells the agent exactly where to get it via get_business_centers_tool. While it does not provide format details, this is sufficient for a single string parameter.

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 a specific action ('Get cash balance and credit limit') and a specific resource ('all advertiser accounts within a Business Center'), and it lists the returned fields. This is distinct from sibling tools like get_advertiser_info_tool or get_authorized_ad_accounts_tool because it focuses on balance and credit limit scoped to a Business Center.

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 gives an explicit prerequisite: 'Use get_business_centers_tool first to get bc_id.' This tells the agent how to obtain the required parameter and establishes a clear call order. It does not spell out when not to use this tool, but the context is sufficient for a simple getter.

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