instagram_media

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: URLs are signed Instagram CDN links that expire after a few hours, and each call costs 1 credit. That expiry and cost detail is exactly the kind of context annotations can't carry.

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-loaded with the core purpose, followed by quality/scope detail, expiry behavior, and cost. No sentence is wasted. Slightly compressed but effective; cost line is well-placed at the end.

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 2-parameter read tool with 100% schema coverage and no output schema, the description covers the return nature (direct image/video URLs), expiry, and cost. Missing only an explicit pointer to sibling tools for related needs, but otherwise complete.

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 the two parameters (url, shortcode) and their examples are already fully documented in the schema. The description adds no syntax, format, or selection guidance beyond it. 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+resource: returns download URLs for a post, reel, or carousel, covering every slide. This distinguishes it from siblings like instagram_post or instagram_posts, though it never names the alternative explicitly. Clear purpose an agent can act on.

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?

Usage is implied rather than stated: an agent infers this is what to call when it needs raw media files. There is no explicit when-to-use vs instagram_post/instagram_posts, no exclusions, and no prerequisites noted. Minimum viable guidance.

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