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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description's only contribution is the 'mirrored' provenance and 'active Meta ads' scope filter, which is modest but genuinely additive context beyond the annotations; it says nothing about pagination limits or result shape.

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?

It is short, but that brevity comes from under-specification rather than economy: a single sentence fragment with no verb and no structure. There is nothing superfluous, but nothing front-loaded or actionable either.

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 six-parameter, zero-required-parameter listing tool with no output schema and partial schema coverage, the description is far too thin. It omits what is returned, how paging/search interact, and what 'mirrored' and 'active' mean operationally.

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 67%, and the description mentions none of the six parameters. It leaves 'platform' (facebook/instagram enum) and 'hidden_only' undocumented in both schema and description, so it fails to compensate for the coverage gap and adds no meaning over the schema that does exist.

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 is a noun fragment, 'Mirrored comments on active Meta ads,' that essentially restates the title 'List Meta comments' without a verb or a clear statement that it lists/returns paginated comment records. The words 'mirrored' and 'active Meta ads' do narrow scope slightly, but they do not tell an agent what operation is performed or how this differs from sibling report_meta_comments or list_meta_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?

There is no when-to-use guidance, no exclusions, and no named alternative. An agent cannot infer from the description whether to call this or the nearby report_meta_comments / get_meta_overlay, nor what an 'active Meta ad' prerequisite means.

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