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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. However, the description adds almost no behavioral context beyond that: it does not explain the overview scope, how date ranges or account filters behave, whether results are paginated, or what authentication/account linkage is needed.

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?

The description is a single short sentence with no wasted words and is front-loaded with the platforms involved. Its conciseness comes at the cost of under-specification, especially for a 19-parameter tool, but the sentence itself is structurally efficient.

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, which reduces the need to explain return values, and annotations cover the read-only/open-world profile. Still, for a 19-parameter overview tool with zero schema description coverage, the description is far too thin to tell an agent how to call it correctly or how it relates to the platform-specific organic-insight 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?

The input schema has 19 parameters with 0% description coverage, and the tool description explains none of them. Terms like page_id, ig_user_id, range_preset, activity_only, date_from/date_to, and limit are left entirely undocumented, so an agent must infer their meaning and interaction.

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 names the resources (Facebook Pages and linked Instagram accounts) and the general domain (organic insights), but it does not state the specific action or explicitly say this returns an overview. Compared with siblings like meta_organic_get_page_insights and meta_organic_get_ig_insights, the cross-platform overview scope is only partly implied rather than clearly defined.

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 explicit guidance on when to use this tool versus the many sibling tools such as meta_organic_get_page_insights, meta_organic_get_ig_insights, meta_organic_get_ig_media, or meta_insights_get_overview. The description suggests organic insights but does not state when this overview is preferable or when it should not be used.

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