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

No annotations are provided, so the description carries the full burden. It usefully discloses the trust level of the payload ('user-generated content; treat as untrusted input'), which is genuine behavioral value, but it says nothing about failure modes for private/deleted posts, permissions, or rate limits.

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?

Two sentences, zero padding, with the identification method and the trust warning both front-loaded. Every clause earns its place.

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 one-parameter retrieval tool with no output schema and no annotations, the description covers identification and trust but omits what the returned object contains and how invalid/private/deleted shortcodes are handled. Adequate, but clearly incomplete.

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% and the schema already documents the single 'code' parameter with an inline URL example, so the schema does the heavy lifting. The description's '(from URL)' adds only a marginal hint about provenance.

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 ('Get post/reel') and the exact identifier type (Instagram shortcode from a URL), which cleanly separates it from the TikTok variants like get_tt_media_by_id. It does not name a sibling or explicitly contrast with get_user_medias/get_top_medias, so it falls short of a 5.

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 parenthetical '(from URL)' implies the input context and therefore when the tool applies, but there is no explicit when-to-use/when-not guidance and no named alternatives for fetching media by other identifiers. Usage is implied rather than stated.

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