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

Adds real value beyond the readOnlyHint annotation: it discloses the plan requirement ('Pro') and, crucially, that the numeric Opportunity Score itself is not returned — only visible in Ads Manager. That caveat prevents an agent from expecting a score in the response. It does not describe response shape or pagination.

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?

Three short sentences, front-loaded with the purpose and examples, then the caveat. The fragment 'Pro.' is terse to the point of ambiguity, but nothing is redundant.

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?

There is no output schema, and while the description usefully warns the score is absent from results, it doesn't indicate what the recommendations payload looks like (item fields, actionability). For a simple single-param read tool with annotations covering safety, this is adequate but with clear gaps.

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?

One parameter (meta_account_id) with 0% schema description coverage, and the description says nothing about it — no ID format, no mention of how to obtain it. Baseline for zero params is 4, but with an undocumented required param the description should compensate and does not.

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?

States a specific verb+resource ('Meta's own optimization recommendations for an ad account') and grounds it with three concrete examples (Advantage+ audience, consolidate ad sets, fix budget limits). It clearly is not get_insights or get_delivery_health, though it never names those siblings to make the distinction explicit.

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?

Implied usage context (account-level optimization opportunities) plus a prerequisite note ('Pro'), but no explicit when-to-use versus get_guardrails or get_delivery_health, and no when-not conditions. The 'Pro' token signals a plan gate but is unexplained abbreviation.

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