instagram_recent_media

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful output context by naming engagement rate, outliers, and per-format averages, but it does not disclose auth requirements, rate limits, pagination, or how the limit parameter affects behavior.

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?

The description is two short sentences and front-loads the core output description. The second sentence adds a focused interpretive note about the per-format split without unnecessary detail.

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?

For a simple read-only tool with one optional parameter and an output schema, the description is largely complete: it explains what data is returned and highlights the most actionable metric. It leaves a minor gap by not relating the tool to sibling Instagram tools or explaining the limit parameter, but the schema and annotations cover the critical invocation details.

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 sole parameter 'limit' has 0% schema description coverage, and the description does not mention it at all. The schema provides type, default, minimum, and maximum, which makes the gap less severe, but the description does not compensate for the missing semantic explanation of how many posts are returned or when to adjust the limit.

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 states a specific resource and data scope: recent Instagram posts with engagement rate, outliers, and average engagement per format. It is clear what the tool returns, but it does not explicitly differentiate itself from sibling tools like instagram_account_overview or instagram_hashtag_top_media.

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 statement that the per-format split is usually the most actionable number implies the tool is useful for Reels-vs-feed comparison. However, it gives no explicit when-to-use guidance and does not name alternatives such as instagram_account_overview or instagram_hashtag_top_media.

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