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 the useful detail that the returned metrics cover reach/views/engagement/follows, but it says nothing about auth requirements, rate limits, or the fact that this is a multi-page/date-range query. With annotations carrying the safety load, this is an adequate-but-thin 3.

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 front-loaded sentence with no waste, which is good structure. But with 17 parameters and a wide scope, that brevity crosses into under-specification rather than tightness, so it earns only a middling score.

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?

The tool is complex (17 optional params, no required fields) and the description addresses almost none of that complexity. The presence of an output schema and the readOnly/openWorld annotations lighten the burden for return values and safety, but an agent still lacks the parameter and scoping guidance needed to call this correctly rather than one of its many siblings.

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?

There are 17 parameters with 0% schema description coverage, and the description mentions none of them. The agent receives no hint about which of page_id, user_id, client_id, site_url, ad_account, campaign_name, property_name, date_from/date_to, days, or range_preset actually matter, nor which are mutually exclusive. This matches the LOW calibration case of many undocumented params at 0% coverage.

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 (get) and resource (Facebook Page organic insights) and even enumerates the metric families returned (reach/views/engagement/follows). It is clear what the tool does, but it does not differentiate itself from close siblings like meta_organic_get_overview or meta_organic_get_ig_insights, leaving the agent to guess which of the several insight tools to pick.

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 no when-to-use guidance, no indication of prerequisites (e.g., a page must be connected), and never names an alternative among the many sibling insight tools. The only implicit cue is the platform word 'Facebook Page', which is not enough to route an agent between this and meta_organic_get_overview.

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