ad_manager_li_get_ad_account_details

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

The description offers no behavioral context beyond what the annotations already declare (readOnlyHint, idempotentHint, destructiveHint). It does not mention response format, authentication needs, or any caveats. Since annotations already cover safety, the description adds no value here.

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 a single, concise sentence with no unnecessary words, front-loading the core purpose. However, it is so brief that it omits any distinguishing or contextual information, making it only slightly above average in structure.

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?

With no output schema and numerous sibling tools, the description is insufficient. It does not indicate what specific ad account details are returned, nor does it help differentiate from other get_ad_account tools. For a simple getter, the description is too minimal to be considered complete.

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 input schema fully documents both parameters (adAccountId and locationId), including the default for locationId, achieving 100% coverage. The description adds no additional semantic meaning, so the baseline of 3 applies.

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 states a clear verb ('Get') and resource ('ad account details'), and the tool name itself is explicit. However, it does not differentiate from sibling tools like ad_manager_li_get_ad_accounts (plural) or platform-specific get_ad_account_details tools, leaving potential ambiguity about which tool to choose.

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?

No usage guidance is provided. The description does not mention when to use this tool versus alternatives such as ad_manager_li_get_ad_accounts or other platform-specific detail retrieval tools. There is no discussion of prerequisites, exclusions, or context for selection.

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