Transcript

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

Adds behavioral details beyond what annotations provide: 'under 2 minutes' limit, 10-30 second response times, null on no speech, and credit consumption requiring confirm=true. However, annotations already declare readOnlyHint=false and destructiveHint=false; the description notes 'Read-like POST requests do not publish to social platforms,' which clarifies the otherwise confusing write-esque annotation.

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?

Front-loads the core purpose first, then adds necessary operational caveats. The sentence about carousel posts and the final sentence about read-like POST requests are slightly extraneous but not harmful.

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?

Complete for a transcript tool with 100% schema coverage and no output schema. The description covers duration limits, response time, null behavior, carousel handling, credit cost, and the confirm requirement, giving an agent everything needed to call it correctly.

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%, so the schema already documents all parameters. The description adds only 'requires confirm=true' and the URL input implication, but nothing beyond the schema's own explanation.

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 verb (Generates transcription) and resource (Instagram video post or reel), clearly distinguishing it from related siblings like tiktok_transcript or youtube_transcript.

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?

Implies usage context via 'Instagram video post or reel' and 'under 2 minutes', but does not explicitly state when to use this vs. e.g. instagram_post_reel_info or when not to use (e.g., for static image posts).

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