ads_get_ad_account

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 operation and mentions 'spending and limits' but does not disclose return format, any required permissions, rate limits, or what 'detailed info' includes beyond those two items. For a simple get, this is minimal disclosure.

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?

A single concise sentence that starts with the verb, names the resource, and specifies key output content. No wasted words and efficiently front-loaded.

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 one parameter and no output schema, the description is modest but covers the core purpose. It is insufficient to fully understand the return structure or any behavioral nuances, but for a simple get on a single account, it provides a minimal viable explanation. The lack of annotations increases the need for more detail, so it is not a 4 or 5.

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 provides one parameter (account_id) with only a type, and the description adds that it refers to an ad account. This is some added meaning, but it does not explain the format (e.g., 'act_...' prefix) or any other details. Given the parameter is self-explanatory and schema coverage is 0%, this is an adequate but not rich contribution.

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 'Get' and identifies the resource 'detailed info for a single ad account' with explicit content 'including spending and limits'. This clearly distinguishes it from sibling tools like ads_list_ad_accounts, since it is about a single account rather than a list.

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 phrase 'for a single ad account' implies the need to already have an account_id and suggests using this when a single account's details are needed, not when listing accounts. However, it does not explicitly state when to use this over alternatives or mention any exclusions.

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