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

Annotations declare readOnlyHint=false, openWorldHint=false, destructiveHint=false, which is surprising for what reads as a reporting tool; the description doesn't clarify any side effect or the reason for the non-read-only flag. It does add useful output context beyond annotations by naming the `catalog` structure and the level→template-variable mapping.

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?

Single tight paragraph with the resource and metric list front-loaded. The nested parentheticals and template-variable notation make it denser than necessary, but no sentence is padding.

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 no output schema and 7 parameters, the description must carry the return shape, and it only partially does: it lists metrics and mentions `catalog`/`series` semantics loosely. The concrete response structure (per-id keying, aggregation units such as currency for revenue/cost) is left unstated.

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 coverage is 86%, so baseline is 3, but the description genuinely earns more: it explains that level maps to a source-template dimension ({{campaign.id}} → ad_campaign, {{adset.id}} → sub2, {{ad.id}} → creative) and that ad_account_id controls the `catalog` output — meaning the schema does not carry.

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?

Description states a specific verb+resource: it returns tracker metrics (clicks, uniques, leads, revenue, profit, ROI, EPC, CR) keyed by Facebook campaign/adset/ad ids, with a `catalog` name mirror. The role is distinguishable from siblings like report_meta_ad_stats through the browser-extension overlay framing, though the jargon ('Torvex columns') makes first-read parsing harder than it should be.

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?

It says the result is 'restricted to the given ids' and that `catalog` exists for name → id matching, which implies intended usage. It never explicitly says when to pick this over report_meta_stats, report_meta_ad_stats, or get_statistics, nor what happens when ids are omitted.

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