Get Facebook Post Insights

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds behavioral context by stating that all metrics use the 'lifetime' period (cumulative from post creation). This goes beyond what annotations provide, though it doesn't cover aspects like rate limits or authentication details beyond page_id.

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 concise and well-structured: a one-line purpose, a prerequisite line, and a bulleted 'Args' section. Every sentence adds value, and the information is front-loaded. No wasted words.

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?

While the description covers the metrics and period well, it lacks explicit information about the return format. There is no output schema, and the description doesn't specify whether the tool returns a JSON object, markdown table, etc. The response_format parameter gives options, but the structure of the output data (e.g., metric names as keys, values as numbers) is not described, which could leave agents uncertain.

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 coverage is 100%, but the description significantly enhances understanding, especially for the 'metrics' parameter. It lists all available metrics grouped by category (Performance, Engagement, Reactions, etc.), which is far more informative than the schema's default array and short description. This empowers the agent to select appropriate metrics.

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 'Gets performance metrics for a specific Facebook Page post', specifying the verb 'Gets' and the resource 'performance metrics for a specific Facebook Page post'. Among siblings like meta_get_post (which gets post content) and meta_get_page_insights (which gets page-level insights), this tool is uniquely distinguished.

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 explicitly lists a prerequisite: 'Requires: meta_list_pages called first.' It also provides guidance on metric categories and the lifetime period. While it doesn't explicitly state when not to use this tool or suggest alternatives, the context is clear enough for an agent to understand when to invoke it.

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