get_advertiser_info_tool

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

No annotations are provided, so the description carries the full burden. It indicates a read-only metadata operation and adds a meaningful behavioral caveat about timezone dependency, but it does not address permissions, response shape, batch size limits, or error behavior. This is adequate for a simple getter but not fully transparent.

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 with no wasted words. The first sentence states exactly what the tool does and what it returns; the second explains why it matters. This is an appropriately sized, front-loaded definition.

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 metadata lookup with an output schema, the description is complete. It tells the agent what will be returned, and why the data is important for interpreting other tools. Nothing critical is missing for an agent to decide to call and correctly invoke this 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?

The schema has 0% description coverage, but the description compensates by specifying the parameter applies to 'one or more advertisers' and explaining what metadata is retrieved. The parameter 'advertiser_ids' is self-explanatory in context, and the description adds meaning beyond the raw schema by clarifying batch usage.

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 uses a specific verb and resource: 'Get account-level metadata' and enumerates the exact fields returned (currency, timezone, industry, status). It also clarifies the tool operates on 'one or more advertisers', which sets it apart from sibling tools focused on campaigns, ads, reports, or business-center assets.

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 clear context for when to use this tool: it is 'foundational context for interpreting all other data', specifically noting date breakdowns depend on the account timezone. It does not explicitly name alternatives or state when not to use it, but the guidance is strong enough to route an agent effectively.

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