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

The description says 'Get', which implies a read-only retrieval operation, but the annotations declare readOnlyHint=false. That is a direct conflict in the safety profile. The description also adds no context about authentication, rate limits, private media behavior, or error handling.

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 a single front-loaded sentence with no wasted words. It immediately communicates the verb, resource, and required identifier.

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?

The tool is simple and has an output schema, so the description does not need to explain return values. However, for an open-world retrieval tool it should clarify behavior enough to resolve the readOnlyHint conflict and provide basic routing guidance among sibling tools.

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 description coverage is 100%, and the shortcode parameter is already well documented in the schema with examples. The description only restates that the tool uses a shortcode, so it adds no meaningful parameter semantics 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 states a specific verb and resource: get a single Instagram post or reel by shortcode. This is clear and distinguishes the tool from profile-oriented siblings in practice, though it does not explicitly name alternatives such as instagram_profile.

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 by the phrase 'by its shortcode', which tells the agent when this tool applies. However, there is no explicit guidance about when to use this versus instagram_profile, api_request, or other media-specific tools.

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