Get Minimum Ad Budgets

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the tool is clearly a safe read. The description adds that it returns minimum budget requirements per bid strategy, which is useful but not critical 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?

Three short paragraphs: purpose, usage note, then args and returns. Every sentence adds value, no redundancy. Front-loaded with the main action and critical usage context.

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 2-parameter read tool with annotations, the description covers purpose, prerequisite, argument with example, return type, and confidentiality (no output schema needed). Sufficient for an agent to use correctly.

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 schema has 50% coverage (only response_format described). The description provides an example for ad_account_id and explains the return structure, adding meaning beyond the schema. Response_format is fully described in schema, so no bonus needed.

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 verb 'Gets', the resource 'minimum budgets for an ad account', and the scope 'by currency and bid strategy'. It differentiates from siblings by specifying it's essential before creating ad sets.

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 states that this tool is essential to check before creating ad sets to avoid API errors, providing clear when-to-use context. No explicit exclusions or alternatives, but the guidance is strong.

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