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

No annotations are provided, so the description carries the burden. It only mentions billing (1 credit per call) but doesn't disclose what the tool returns, whether it's read-only, or any side effects. The billing note is useful but insufficient.

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 very short and front-loaded with the tool's purpose. The billing note is extra but relevant. No wasted words, though it could be slightly more informative.

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?

Given the tool's simplicity (one param, no output schema), the description is minimal but lacks context about what 'Reel Media' includes, how the shortcode is used, or what the response looks like. The billing note is the only extra context.

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% with a single 'shortcode' parameter, and the description doesn't add meaning beyond the schema. The schema already provides the parameter name and example, so the description adds no extra value. Baseline 3 is appropriate.

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 the tool gets Instagram Reel Media, which is a specific resource, but it doesn't clearly distinguish from sibling tools like get_reels_posts or get_post_info. The verb 'Get' is generic and the resource 'Reel Media' is somewhat vague.

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 this tool versus alternatives. The description only mentions billing per call, which is not usage guidance. It doesn't explain what 'Reel Media' means or when to prefer this over get_reels_posts.

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