facebook_page_insights

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

No annotations are provided, so the description carries the full burden. It only states the tool retrieves statistics, which implies a read operation, but lacks disclosure of behavioral traits such as authentication requirements, rate limits, pagination, or whether data is real-time. Minimal behavioral context.

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 sentence, front-loading the verb and resource. It is concise with no wasted words. However, given three parameters, slightly more detail could be included without harming conciseness.

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 description is terse and lacks output schema. It does not mention the return structure, any limitations (e.g., date range, data freshness), or how to interpret results. For a simple retrieval tool, more context would help the agent understand what to expect.

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%, so each parameter already has a description. The tool description adds examples of metrics (views, reach, engagement), which overlaps with the metrics parameter. No additional parameter meaning beyond what the schema provides; baseline of 3 is appropriate.

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 the tool retrieves Facebook Page statistics including views, reach, and engagement. The verb 'Récupère' and resource 'une Page Facebook' are specific. The examples differentiate it from sibling tools like facebook_list_pages (listing) and facebook_post_feed (posting).

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 implies usage when page statistics are needed, but no explicit guidance on when to use this tool vs alternatives, prerequisites, or exclusions. Sibling tools are functionally distinct, so the context is somewhat implied.

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