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

Annotations declare readOnlyHint=false and destructiveHint=false, which are minimal. The description adds important behavioral detail: it specifies that text formats return inline content while DOCX/ZIP return base64, and notes that the filename extension drives detection. This provides value beyond the schema and annotations.

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 concise (three sentences) and front-loaded with the primary action. Every sentence serves a purpose: listing input types, instructing how to pass content, and specifying output format. No filler or redundancy.

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 conversion tool with 4 parameters and no output schema, the description covers the key elements: input types, how to supply content, target selection, format detection, and return format. It omits potential edge cases (e.g., error handling) but these are not critical given the tool's straightforwardness. The description is sufficient for an agent 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 a baseline of 3 applies. The description adds meaning by explicitly mapping `content` to text formats and `content_base64` to binary (.prtranscript), which clarifies the intended usage beyond the generic schema descriptions. It also clarifies the `target` parameter's default behavior.

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 explicitly lists the supported input types (subtitle, transcript, caption, EDL, FCPXML, .prtranscript) and the action (convert), making the tool's purpose unambiguous. It clearly distinguishes from siblings like list_converters and inspect_file, which serve different functions.

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?

The description provides concrete guidance: to select a target, use `list_converters`, or rely on the "auto" default. It also explains that the filename extension drives format detection, giving an implicit usage context. It does not explicitly state when not to use this tool, but the reference to `list_converters` for targets covers the main alternative.

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