meta get account details

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds no behavioral context such as required permissions, rate limits, or error conditions, but it also does not contradict the annotations.

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 one concise sentence that front-loads the action and resource, then lists the relevant fields. Every word earns its place, with no redundant phrasing or filler.

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?

Given the simple one-parameter schema, rich safety annotations, and an output schema, the description is sufficient. An agent can correctly select and invoke this tool for a targeted account-details lookup without needing additional context.

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 single parameter adAccountId is fully described in the schema, including an example format (act_123456789). The description adds no further parameter meaning beyond confirming the target is a specific ad account, so it provides no extra value here.

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 and resource ('Get detailed information for a specific Meta ad account') and enumerates concrete data fields (name, currency, timezone, spend cap, status, business info). This clearly distinguishes it from sibling list-style tools like meta_list_ad_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 'for a specific Meta ad account' phrasing implies a targeted single-account lookup, which is useful context versus listing tools. However, it does not explicitly state when to prefer this tool, what prerequisites exist, or how it relates to alternatives like meta_list_ad_accounts.

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