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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond them: no default time window behind 'recent', no pagination behavior for limit, no note on whether an authenticated page connection is required for the 17 optional identifiers. With the annotation bar lower a 2 reflects that the text contributes essentially zero new behavior.

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 a single short fragment, which is superficially concise but reflects under-specification rather than editing: for a 17-parameter tool the absence of substance is the problem, not the length.

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?

An output schema exists, so return-value detail is not required, but the description leaves the agent with no parameter guidance, no time-range semantics, and no sibling routing for a tool with 17 optional, undocumented inputs. It is far short of complete for this complexity.

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 0% across 17 parameters (url, days, limit, sort_by, range_preset, activity_only, etc.), so the description carries the full documentation burden and supplies none of it. No parameter is mentioned, no format or default is explained, and no interaction between date_from/date_to/days/range_preset is clarified.

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?

Names a specific resource (Facebook Page posts) with a scope qualifier ('recent') and an indication of the payload ('with engagement'). It is clear what is returned, but it never distinguishes itself from close siblings such as meta_organic_get_page_insights or meta_organic_get_ig_media, so an agent cannot route between them from the text alone.

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 mention of alternatives despite several overlapping organic/insights siblings. The only implicit signal is 'Page posts' versus 'IG media', which is left for the agent to infer.

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