get_gql_user_medias

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

Adds meaningful context beyond annotations: pagination mechanism (one page per call, cursor), billing per call, and that it is a live Instagram request. Annotations already cover read-only and open-world safety, so the description enriches rather than duplicates. Does not detail rate limits or response shape, but this is solid.

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?

Front-loads the core purpose in the first sentence, then covers alternatives, parameters, and billing in compact sentences. Every sentence adds distinct value with no 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?

Complete for a paginated read tool: covers purpose, alternatives, pagination flow, parameter usage, billing, and endpoint. No output schema exists, and the description does not describe the response structure, but for a list tool with a cursor pattern this is largely adequate.

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 33%, so the description must compensate. It explains that user_id identifies the account, that profile_grid_items_cursor is the cursor from the previous response for pagination, and that flat flattens nested objects. This adds significant meaning beyond the schema for two of three params, though user_id format is still unspecified.

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 posts') and explicitly differentiates from siblings get_v2_user_clips (reels) and get_v2_user_tag_medias (tagged posts). Includes the endpoint for disambiguation.

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?

Explicitly says when to use this tool ('read an account's feed') and names the alternatives for reels and tagged posts with their distinguishing conditions. No inference required.

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