Get Ad Account Details

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description needs only to add context; it does not. The phrase 'detailed information' is consistent with these annotations but adds no further behavioral detail such as response size, rate limits, or required permissions.

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 sentence plus a tight argument listing, with no redundant words. It front-loads the purpose and presents the parameter example in a structured way.

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 simple read-only getter, the description and schema together cover the required parameter, an optional output format, and the tool's purpose. It omits details about the response contents, but with no output schema and a standard 'detailed information' phrase, this is a minor gap; the sibling list provides plenty of context that this is an ad account detail lookup.

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 description documents the required ad_account_id parameter with a concrete example ('act_123456789'), compensating for the schema's lack of description for that field. It does not mention response_format, but the schema already describes it fully, so effective coverage is high.

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 states the tool's function: 'Gets detailed information about a specific ad account.' This distinguishes it from list-type siblings like meta_list_ad_accounts by emphasizing a single account, though it doesn't explicitly name alternatives.

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 guidance is given about when to choose this tool over sibling tools such as meta_list_ad_accounts or meta_get_ad_account_activity. The intended use is only implied by the name and the required ad_account_id parameter, leaving an agent to infer the selection context.

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