get_v2_user_clips

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

Annotations already cover read-only and open-world safety. The description adds genuinely useful context beyond them: it is a live request to Instagram, it is billed per call, it returns one page at a time, and the underlying endpoint. These are traits the schema and annotations cannot convey. Missing only rate-limit or quota detail.

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 sentences, front-loaded with the scope constraint and routing rule, then the pagination mechanics, then the deployment and billing facts. Every sentence earns its place with zero filler.

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?

No output schema, so the description must carry the return shape. It does: one page per call plus the next_page_id handoff. Combined with annotations and a fully covered schema, an agent has everything needed to call and chain this tool 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 coverage is 100%, so all three parameters are already documented. The description reinforces the pagination handoff (page_id from next_page_id) and names user_id, but adds no syntax or format detail the schema lacks. Baseline 3 applies when the schema does the heavy lifting.

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 specific verb and resource ('List an Instagram user's reels') and explicitly distinguishes the tool from its closest sibling by naming `get_gql_user_medias` and contrasting scope ('reels only' vs 'all posts'). An agent can route between the two without opening either schema.

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?

Names the alternative and the condition that selects it ('Use it for reels only; use get_gql_user_medias for all posts'). Also supplies a concrete conditional flow for pagination: pass next_page_id as page_id on the following call.

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