Get Instagram Media

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

Annotation already marks readOnlyHint=true, consistent with 'Fetch'. Description adds that it targets one media object, but no additional behavioral traits (e.g., no mention of required parameters, rate limits, or response structure).

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?

Single sentence, no wasted words. However, could be slightly more informative without adding length (e.g., mention required parameter).

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?

No output schema, many sibling tools, and 3 parameters with zero coverage. Description fails to explain what metadata fields can be requested, how to use the fields parameter, or any authentication prerequisites.

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 0%, and description adds no meaning to the 3 parameters (mediaId, fields, accessToken). Does not explain purpose or format of any parameter.

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?

Description clearly states verb ('Fetch') and resource ('metadata for one Instagram media object'). Distinguishes from siblings like meta_list_media (list) and meta_get_top_media (top media) by specifying single media object.

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?

No guidance on when to use vs alternatives. Does not mention prerequisites (e.g., need access token, media ID) or when not to use (e.g., for listing media).

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