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

The annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds no behavioral context such as data freshness, authentication requirements, typical latency, or whether it aggregates multiple sources. With 17 parameters and no explanation of their effects, the behavioral burden is far from met.

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, which is concise but fails to front-load essential information due to its extreme brevity. It reads more like a label than a functional description, wasting the opportunity to guide the agent.

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?

For a tool with 17 parameters, 0% schema description coverage, and a complex multi-entity scope, the description is drastically incomplete. It does not help the agent understand parameter usage, data returned, or when to prefer it over siblings, making it inadequate even considering the output schema.

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 schema provides only names and types with no meaning. The description does not mention or explain any of the 17 parameters (e.g., url, days, page_id, ig_user_id), leaving the agent entirely uninformed about what they control.

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 domain (organic insights), which is clearer than the bare title. However, it lacks a specific verb like 'retrieve' or 'aggregate' and gives no indication of what the overview contains, leaving the agent to infer the action from the name.

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 guidance on when to use this tool versus the many sibling organic tools (meta_organic_get_ig_insights, meta_organic_get_page_insights, meta_organic_get_page_posts, meta_organic_get_ig_media). The description does not mention any alternative or condition for selection.

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