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

With no annotations, the description must carry the full behavioral burden, and it does disclose the key traits: format is retained unless qc=true, and regenerate applies saved QC edits before export. It omits whether the export writes to output_path overwriting existing files, whether it requires permissions, and whether regenerate has side effects on stored state.

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 core output behavior is front-loaded in the first sentence, and subsequent sentences are tight flag guidance with no filler. Slightly choppy fragmentation but no wasted content.

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?

The output schema covers return values, so the description needn't explain them, and the format/qc/regenerate behavior is covered. For a no-annotation tool with five parameters, the unexplained required storage_path and source_language leave a meaningful completeness gap.

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%, so the description must explain all five parameters; it explains qc, regenerate, and the extension convention for output_path. It says nothing about storage_path (a required parameter) or source_language, so two of five parameters, including one that is mandatory, remain opaque.

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 and resource ('Export a saved subtitle or its QC workbook') plus the return form ('file/download URL'), so the agent knows exactly what happens. It does not name or contrast with the closest sibling, get_subtitle_download_url, leaving the agent to infer which one to call.

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?

Gives real conditional guidance for two flags: 'Set qc=true for the review XLSX' and 'regenerate=true applies saved QC edits first.' However, it never says when to prefer this over get_subtitle_download_url or how it relates to get_subtitle_review/update_subtitle_review, so the when-vs-alternative question is unanswered.

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