list_media

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

With no annotations, the description carries the burden of disclosing behavior. 'List' conveys a non-mutating operation and 'with basic engagement counts' hints at return content, but it does not mention ordering, pagination, rate limits, or whether this requires special permissions. For a simple list tool this is adequate but not rich.

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 one efficient sentence, front-loaded with the primary action ('List recent media') followed by concise clarifiers for scope and return content. Every element 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?

For a single-parameter list tool with no output schema, the description identifies the resource and return value type but does not specify the output shape or pagination behavior. It is usable, but an agent might still be unsure about the exact media object fields beyond engagement counts.

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 needed to explain the 'limit' parameter. It does not mention limit at all, leaving the agent to rely solely on the schema's min/max/default metadata, which is clear but not supplemented by the description.

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?

Description states a specific verb ('List'), a specific resource ('recent media on the connected Instagram account'), and names the media types included. It is clearly distinct from siblings that create/schedule content or return insights for a single media item.

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 makes the read-only listing purpose obvious, which implies use when the agent needs recent media and engagement counts. However, it does not explicitly say when to prefer this over siblings like get_media_insights or list_scheduled_posts, leaving routing to inference.

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