Get profile analytics

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds value by disclosing the return structure, particularly the Instagram demographic breakdowns with nested objects for follower_demographics and engaged_audience_demographics.

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: the first succinctly states the tool's purpose, the second adds specific return details for Instagram. Every sentence earns its place with no redundancy.

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?

Given the existence of an output schema, the description adequately covers the purpose and key return value details. It could mention time range or pagination, but it is complete enough for the tool's complexity.

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 does not elaborate on any of the four parameters beyond the schema's own descriptions. Schema coverage is high (75% with descriptions for three of four parameters), so the baseline is 3, and the description adds no additional parameter context.

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 aggregated analytics for a profile across selected platforms, specifying metrics like followers, views, engagement. It also details Instagram-specific return fields. However, it does not explicitly differentiate from sibling tools like get_platform_metrics or get_total_impressions, which might be ambiguous.

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 implies usage for profile-level analytics across multiple platforms. It provides no explicit guidance on when to use this tool versus alternatives like get_post_analytics for per-post analytics or get_platform_metrics for specific metrics.

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