ads_get_customer

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

No annotations exist, so the description must carry the behavioral disclosure burden. It only states 'Gets details,' which implies a read operation, but does not mention auth requirements, rate limits, error behavior, or what fields are included in the 'details.' For a tool with no annotations, this is insufficient.

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?

One direct sentence with no filler. It is front-loaded with the verb and resource and is appropriately sized for a single-parameter getter.

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?

The tool has no output schema, so the description should indicate what 'details' means (e.g., account name, currency, time zone, status). It does not, leaving the return shape underspecified. For a simple tool with one parameter, this is a notable gap, though the tool's low complexity prevents a lower score.

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 100%, so the schema already documents customerId as a string without dashes. The description adds no additional meaning to the parameter; it only refers to the customer account generally. Baseline 3 applies because the schema carries the semantics.

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 ('Gets') and a specific resource ('details of a specific Google Ads customer account'). It clearly differentiates from siblings like ads_list_customers (specific vs list) and ads_get_campaign (customer account vs campaign). No ambiguity about what the tool acts on.

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 no guidance on when to use this tool versus alternatives such as ads_list_customers or ads_account_summary. No exclusions or prerequisites are mentioned, leaving the agent to infer the use case from the name and schema.

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