list_recent_media

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

With readOnlyHint and openWorldHint already provided by annotations, the description adds useful behavior: newest-first ordering, exclusion of stories, absent like_count when likes are hidden, and a has_more indicator for older media. It does not discuss permissions or rate limits, but the key read-only list semantics are covered.

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 front-loaded and efficient, leading with purpose and usage before arguments and return details. The Returns block repeats fields already available in the output schema, but it still earns some of its space by noting hidden like_count behavior and has_more.

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?

This is a simple one-parameter read tool with an output schema, and the description supplies what the schema does not: purpose, sibling routing, limit semantics, ordering, exclusions, and key return caveats. An agent has enough information to invoke it correctly.

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 for the single limit parameter. It does so fully by documenting that limit controls how many items are returned, accepts 1-100, and defaults to 10.

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 verb and resource: it lists the account's most recent posts and reels, newest first, and explicitly excludes stories. It also distinguishes itself from sibling tools by saying it helps find media IDs for get_media_comments and get_media_insights.

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 gives explicit usage guidance: use it to find media IDs for comment/insight tools or to review recent content and engagement. It also names the relevant sibling tools, so an agent can route correctly without inference.

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