list_ig_media

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

With no annotations, the description carries the behavioral burden. It does add useful traits beyond the tool name: results are limited to recent publications and to posts/reels/carousels. However, it does not clarify the meaning of 'recent', mention pagination/ordering, or note any authorization requirements, so it is only minimally 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?

The description is a single front-loaded sentence with no filler; the verb and object come first and the parenthetical adds useful scope. It is appropriately sized for a simple list operation.

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 two-parameter tool with an output schema, this is a minimum-viable definition: an agent can likely invoke it with ig_user_id and optional limit. But missing usage alternatives, parameter explanations, and behavioral details leave clear gaps that prevent full confidence in correct selection.

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 0%, so the description must compensate, but it does not explain ig_user_id or limit. The tool name and schema titles make some inference possible, but the description adds no explicit meaning beyond 'Instagram publications'.

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 uses a clear verb ('List') and resource ('publications Instagram') and enumerates included media types (posts, reels, carrousels), so an agent can tell this is a list operation for Instagram media. It does not explicitly distinguish itself from sibling tools like get_ig_media or list_ig_stories, so it stops short of a 5.

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?

There is no guidance about when to choose this tool instead of the many similar Instagram siblings, and no exclusions or conditions are given. The only implied usage is that it lists recent media, which the agent must infer from the description itself.

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