instagram_get_media

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds valuable behavioral context by enumerating the return fields and noting that album_items[] are included for multi-photo posts, which is a conditional behavior not captured in annotations.

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 efficiently structured: purpose sentence, usage context, then Args/Returns sections. Every sentence earns its place, and the content is front-loaded with the most actionable information first. No fluff.

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 read-only tool with an output schema (indicated by signals), the description provides adequate context: when to use it, what to pass, and what to expect in return. Nothing critical is missing for correct invocation.

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?

The schema description covers 100% of the single parameter, including examples. The description repeats the accepted formats (URL, shortcode, or numeric ID) without adding new semantics. Baseline 3 is appropriate since the schema already 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?

The description clearly states 'Get everything about one post' and specifies the key included data (media URLs, tagged users). It distinguishes itself from listing tools and media-specific tools by targeting the full post entity, making it easy for an agent to select among the many Instagram siblings.

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 'Use after a listing tool when you need the full caption, the downloadable photo/video URLs, or the contents of an album.' This gives both the timing (after listing) and the specific triggers, effectively guiding the agent away from alternatives like media comments or user media lists.

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