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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds meaningful extra behavior by disclosing bulk execution support and how scope is resolved using account and customer_id. It does not contradict annotations and provides useful operational context beyond the safety hints.

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 compact and front-loaded: the first sentence states the core purpose and outputs, and the second sentence adds the bulk behavior cleanly. No filler words or unnecessary repetition of schema properties.

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 no output schema, the description tells the agent what fields will be returned and how scope is resolved. It could be more detailed about required parameter combinations and bulk execution semantics, but for a simple lookup tool the description is largely sufficient.

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 description coverage is 0%, so the description carries the burden for explaining the parameters. It does explain that account and customer_id resolve scope and that customer_ids enables batched execution, but it leaves ambiguity around whether one is sufficient, whether both are required, and what exactly account represents in relation to customer_id.

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 identifies the tool's action ('Get Google Ads account info') and specifies the returned fields (name, currency, timezone), making its purpose concrete. It also distinguishes itself from sibling tools by focusing on a single customer's account info rather than listing accounts or managing campaigns.

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 provides useful context: the tool targets a specific customer and uses account + customer_id to resolve scope. It also notes bulk support via customer_ids, but it does not explicitly state when to prefer this over alternatives like google_ads_list_accounts, so it lacks explicit exclusion guidance.

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