instagram_posts

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuinely new behavior: page size (12), ordering (newest first), the exact field set returned, cursor-based paging, and a 1-credit cost. That cost and payload disclosure is real value beyond the structured fields.

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?

Three short sentences, tightly front-loaded with purpose, payload shape, and cost. Nothing is padded and no sentence restates the name.

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?

With no output schema, the description usefully enumerates return fields plus page size and ordering. It omits any note on what happens when both user_id and username are absent or how many pages are available, but is otherwise sufficient for a read-only paging tool.

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 100% and each parameter (cursor, user_id, username) is documented in the schema, so the baseline is 3. The description only restates cursor paging ('Page with cursor') without adding format or fallback semantics beyond what the schema already states.

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?

States a clear verb ('Get') and resource ('recent Instagram posts'), and pinpoints the returned payload. However, it never distinguishes itself from near siblings such as instagram_post (single post), instagram_media, instagram_tagged, or instagram_reels, so an agent must infer the boundary from the name alone.

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 no when-to-use guidance and names no alternative. It never explains when to prefer this over instagram_tagged, instagram_place_posts, or instagram_post, leaving sibling selection entirely to inference.

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