get_account_insights

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

Discloses that available metrics vary by Graph API version and that mismatches cause informative errors. However, with no annotations, it does not state whether the operation is read-only, destructive, or has side effects.

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 concise sentences providing key information without redundancy. The first sentence is a clear summary, followed by parameter details and a helpful behavioral note. Could be slightly more structured but is efficient.

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?

Covers the tool's purpose, parameter options, and a behavioral caveat. However, omits the 'account' parameter entirely and does not differentiate from similar analytics tools, leaving gaps in 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?

Adds meaning to 'metrics' and 'period' parameters beyond the schema, including defaults and allowed values. The 'account' parameter is not described, and the schema has no descriptions (0% coverage), so the description partially compensates but misses one parameter.

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?

Clearly states it provides account-level analytics (reach, impressions, profile views, follower count). Differentiates from per-media tools like get_media_insights by specifying 'account-level', though not explicitly contrasting with siblings.

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 explicit guidance on when to use this tool versus siblings such as get_media_insights or get_audience_insights. Only implicit through the 'account-level' phrasing.

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