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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful behavioral context about being a flattened action and supporting bulk execution via arrays. It does not add details on pagination, rate limits, or output format, but the annotation coverage lowers the burden. No contradiction with annotations.

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 includes a four-action list even though only post_insights is the actual flattened action, adding unnecessary clutter. The '[Flattened action: post_insights]' note and bulk support line are useful, but the action list could be substantially trimmed. It is not appropriately sized for the tool's actual purpose.

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 has 6 parameters and no output schema, and the description provides no explanation of return values or how the output is structured. It also does not clarify the relationship between the multiple actions listed, the flattened action, and sibling tools like meta_ads_pages_insights. Bulk support is mentioned, but period/auth_account semantics are absent, making the contextual picture incomplete.

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%, so the description must compensate. It explains page_id and post_id via the action descriptions and page_ids/post_ids via the bulk support sentence. However, it does not explain the 'period' parameter (beyond the schema enum) or 'auth_account', leaving a gap for those parameters. The ID semantics are clear, but the compensation is incomplete.

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 states 'Read Facebook Pages data' and lists actions, with a direct definition of 'post_insights — detailed insights for a specific post'. However, listing list/insights/posts alongside post_insights creates ambiguity about the actual scope, especially since the actual tool is '[Flattened action: post_insights]'. It does not clearly differentiate from sibling tools like meta_ads_pages_insights or meta_ads_pages_posts.

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 alternatives such as meta_ads_pages_insights or meta_ads_pages_posts. The description implies usage for detailed post-level insights and mentions bulk support with page_ids/post_ids, but it does not state exclusions or situational recommendations. This is less than the 'implied usage' threshold because the action list muddles the intended context.

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