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

Annotations already establish readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context in the credit cost ('2 credits') and the sub-2-minute input limitation. It says nothing about failure modes, e.g. reels without speech, private content, or missing captions, which is the main remaining gap.

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 short fragments with zero filler and the core purpose front-loaded. The telegraphic style is efficient but slightly cryptic; the credit note sits in parentheses where a reader could miss it.

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 single-parameter read tool this covers the essentials, and no output schema exists so return values arguably should be described. Nothing is said about the transcript's shape, language handling, or what happens when no transcript is available.

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?

Only one parameter, and the schema documents it at 100% coverage ('Instagram reel URL'). The description adds nothing about URL format, accepted variants, or whether shortcodes versus full URLs work, so it neither helps nor hurts beyond the schema baseline.

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 resource and output: a transcript of an Instagram reel. The parenthetical scope note ('videos under 2 minutes') narrows the domain usefully. It stops short of a full verb phrase and never restates the platform, but the name plus description together leave no ambiguity about what comes back.

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?

Implied usage only: an agent can infer this applies to reels rather than posts or profiles via the length constraint. There is no explicit when-to-use guidance and no routing against nearby siblings such as instagram_post, instagram_user_reels, or the parallel tiktok_transcript/youtube_transcript tools.

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