get_account_insights

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

Substantial disclosure beyond the annotations: the call hits Instagram live, is slow, and consumes Meta rate-limit quota. It also documents the exact failure mode (403 permission_required) and the remedy (reconnect the account with the insights permission in the portal) — behavior an agent could not infer from readOnlyHint/idempotentHint.

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 short sentences with no filler: what it returns, then the operational cost, then the failure mode. The opening 'Get account insights' is a mild restatement of the name, but it front-loads the scope and metrics immediately after.

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 no output schema, the description compensates by enumerating the returned metrics, and for a single-parameter read tool it also covers latency, rate limits, and the permission error path. Nothing an agent needs in order to call it correctly and interpret a failure is missing.

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 description coverage is 100% and the enum already constrains the single parameter, so the description's mention of 'last 1, 7 or 30 days' adds no new semantics. The schema-implied default of 7 is not reiterated, which is fine given full coverage.

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 names a specific verb and resource and enumerates the exact metrics returned (reach, profile views, interactions, saves, shares, follows), scoped to 'your own account' — which separates it from competitor-facing siblings like get_competitor_leaderboard and get_audience_demographics.

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?

It states the eligible time windows (1, 7 or 30 days) and makes clear this is a live Instagram call that costs latency and rate-limit budget, which implicitly tells an agent to call it sparingly and not inside tight loops. It does not explicitly name alternatives (e.g. get_overview or get_audience_demographics) for related metrics, so routing between them is left to inference.

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