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

No annotations exist, so the description carries the full burden. It does usefully disclose that each request costs 1 credit and requires a Bearer API key, but it never explains what 'public details' actually contains, what happens on an invalid or private shortcode, or whether failures are still billed.

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 core sentence is front-loaded and short. It loses a little polish: there is a double period, and the 'Platform=instagram resource=media/info' fragment is machine-generated boilerplate that duplicates the tool name.

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?

A simple one-parameter read tool, and the auth/cost facts are covered. But no output schema exists, so the description should sketch the shape of the returned media details. Instead it leaves that undefined, which is the main remaining gap.

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?

There is one required parameter, and the schema already documents all three accepted forms at 100% coverage. The description simply repeats those forms, adding no extra syntax or format detail beyond the schema.

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 gives a specific verb and resource: fetch public details for a single post or Reel, keyed by shortcode, URL, or media id. That is enough to separate it from instagram_media/comments or instagram_profile/media, though no sibling is named explicitly.

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?

It states the accepted identifier forms but gives no when-to-use guidance: nothing says to prefer this over instagram_profile/media for listing a profile's posts, nor does it exclude private or story content beyond the word 'public'.

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