get_post_analytics

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

No annotations are provided, so the description carries full burden. It discloses pagination behavior, notes that certain metrics are silently ignored (Instagram click metrics) or cause errors (invalid metrics like 'lifetime.reach'). It lacks explicit mention of read-only nature or authorization requirements, but overall good disclosure.

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?

Three sentences: purpose, pagination guideline, and critical parameter note. Each sentence is essential, and the most important info (pagination, page placement) 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?

With 6 parameters (4 required) and no output schema, the description covers pagination and parameter pitfalls but does not describe the response structure beyond paging info. For a data-retrieval tool, more detail on the return format (e.g., list of posts with metrics per post) would improve completeness.

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 baseline is 3. The description adds value by explaining pagination handling and the page parameter location, and by listing invalid metrics that would cause errors, which goes beyond the schema descriptions.

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 'Get post-level analytics (impressions, engagements, etc.) for posts within a date range.' This uses a specific verb ('Get'), resource ('post-level analytics'), and scope ('within a date range'), distinguishing it from siblings like 'get_profile_analytics' which targets profiles.

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 provides strong usage guidelines including pagination instructions ('always check paging.total_pages and pull all pages') and a critical reminder about the page parameter placement. However, it does not explicitly compare with sibling tools or state when to use alternative tools like 'get_profile_analytics'.

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