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

No annotations are provided, so the description carries the behavioral disclosure burden. It frames the operation as a 'structural snapshot' and lists read-only aggregate contents, which reasonably implies no mutation, and it adds a 30-day time window. However, it does not explicitly state read-only behavior, permission requirements, or any other operational characteristics.

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?

Two sentences with no filler: the first enumerates the summary contents in a compact list, and the second states the intended use case. It avoids repeating schema information and is front-loaded with the most useful detail.

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 no annotations and no output schema, the description covers what the agent can expect to receive and when to use it. The exact return format is not described, but the content list and the schema's parameter documentation are sufficient for tool selection and invocation.

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 description coverage is 100%: the only parameter, ad_account_id, is already documented with the requirement to include the 'act_' prefix. The description adds no additional parameter-level meaning, so the baseline score 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 names the resource (Meta ad account) and specifies the exact contents of the summary: campaign counts by status/objective, ad set counts, active ad count, budget allocation, top spending campaigns, and disapproved ads. It is clear and specific, though it does not explicitly differentiate itself from sibling getters like adsap_get_account_health.

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 description gives clear usage context: use this tool to get the 'big picture before detailed audit.' It implies the tool is for high-level orientation rather than deep analysis, but it does not name alternatives or state when not to use it.

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