get_account_insights

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

No annotations are provided, so the description carries full burden. It implies a read-only operation with 'Get' and lists return metrics, but does not explicitly state idempotency, authorization requirements, or side effects. Adequate but not fully transparent.

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: first sentence states purpose with concrete metrics, second explains key parameter and adds usage hint. No redundant information, every part earns its place.

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 an output schema present, return values need not be detailed. The description covers the main metrics and period options. Minor omissions like time zone handling or error behavior do not significantly impact completeness for a simple read tool.

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 value beyond the schema by explaining the meaning of each enum value for 'period' (e.g., 'day' for last 24h). Since schema coverage is 100%, baseline is 3, and the extra explanation raises it to 4.

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 explicitly states the verb 'Get' and the resource 'account-level insights' with specific metrics (reach, impressions, profile views, follower growth). This clearly distinguishes it from sibling tools like get_media_insights (per-post) and get_ad_insights (ads).

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 explains the period parameter values and suggests usefulness for content strategy decisions, but does not explicitly state when to use this tool versus alternatives like get_media_insights or get_ad_insights. Usage context is implied rather than explicit.

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