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

Annotations indicate readOnlyHint=true and destructiveHint=false, which the description aligns with by stating 'Read Facebook Pages data.' The description adds value by specifying the actions are read-only and mentions bulk execution, which is not in annotations. No contradiction found.

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 fairly concise and uses a bulleted list for actions, but it includes a redundant line '[Flattened action: posts]' which is unclear and adds noise without clear benefit.

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?

Given the tool has 6 parameters and no output schema, the description provides the basics (actions and sample fields) but misses critical details like the full set of parameters (period, auth_account) and any return structure. However, the read-only annotation mitigates some complexity, making it minimally complete.

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 schema has 0% coverage and 6 parameters, but the description only hints at page_ids, post_ids for bulk and the page_id for insights. It does not explain the meaning of period, auth_account, or the distinction between page_id and page_ids, leaving the agent to infer usage.

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 clearly states it reads Facebook Pages data and enumerates four action types (list, insights, posts, post_insights) with specific fields (e.g., name, fan_count, likes). However, it does not distinguish these actions from sibling tools like meta_ads_pages_insights and meta_ads_pages_list, which likely overlap.

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?

Description mentions bulk support but gives no guidance on when to use this tool versus sibling tools like meta_ads_pages_insights or meta_ads_pages_post_insights. It does not specify the context for each action or when to prefer a more specialized tool.

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