get_page_insights

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

With no annotations provided, the description must disclose behavioral traits. It mentions deprecated metrics but does not state that the operation is read-only, require authentication, or have any side effects. The term 'retrieve' implies non-destructive read, but explicit safety context is missing.

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?

Two sentences with a front-loaded purpose, followed by supported features and a note. No redundant or unclear language. Every sentence contributes meaning.

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?

Despite having 6 parameters and no output schema, the description omits key context: it does not explain that date_preset and since/until are mutually exclusive, does not describe the response format or default behavior, and lacks info on required auth. The note on deprecated metrics is helpful but insufficient for full 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?

The description adds a summary of supported metrics and periods (day/week/days_28) that mirrors the schema. Since schema description coverage is 100%, the description does not add new parameter details; it reinforces existing info. Baseline 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 it retrieves page-level analytics and lists specific metrics (e.g., page_views_total, page_fans). The verb 'retrieve' and resource 'page-level analytics' are precise, and the scope distinguishes it from sibling tools like get_post_insights (post-level) or get_page_info (page settings).

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?

No guidance on when to use this tool versus alternatives (e.g., get_post_insights) or when not to use it. There are no prerequisites, exclusions, or contextual hints beyond the implicit page-level scope.

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