ads_get_account_details

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

With no annotations provided, the description carries the burden of communicating behavior. 'Get details' clearly indicates a read operation rather than a mutation, and the listed fields define what the agent can expect to learn. It does not discuss auth or edge cases, but for a simple getter the behavior is reasonably 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?

The description is compact and front-loaded with the core purpose, followed by the only parameter's semantics. Every sentence adds value and there is no redundant phrasing.

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 single-parameter read tool with an output schema present, this description is complete: it states what is retrieved, the parameter format/default, and the scope. Nothing needed for correct invocation appears missing.

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 coverage is 0%, but the description fully compensates: it explains customer_id is a 10-digit account id, that dashes are acceptable, and that it defaults to the environment default. This adds meaningful format and fallback semantics beyond the schema.

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 starts with a specific verb and resource: 'Get details for a single account.' It enumerates the returned fields (name, currency, time zone, status, etc.) and the 'single account' scope differentiates it from sibling tools like ads_list_accounts.

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 'single account' framing clearly signals this is for retrieving one account's detail, with the optional customer_id defaulting to the environment default. It does not explicitly name alternatives or provide exclusion criteria, so it stops short of fully explicit routing guidance.

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