list_subtitles_contents

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safe read-only nature is covered. The description adds no additional behavioral traits such as behavior for null paths, file-not-found handling, or encoding/return format details.

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 short, front-loads the core purpose, and includes a useful endpoint line plus an args block. No filler, though the args line adds little beyond the schema.

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?

With only one optional parameter and an output schema present, the tool is simple to call. The description covers the endpoint and parameter but omits the meaning of the default null and any preconditions for obtaining a subtitle_path, leaving a modest 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 compensate. Saying subtitle_path is 'Subtitle filepath' essentially restates the property name and title, and does not clarify whether it is absolute/relative, what formats are supported, or what null/default means.

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 begins with a precise verb and object ('Retrieve subtitle file contents'), telling an agent exactly what resource is affected. It is differentiated from list_subtitles and list_subtitles_info by the word 'contents', though it does not explicitly name a sibling.

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?

There is no guidance on when to choose this tool over list_subtitles or list_subtitles_info, no exclusions, and no mention of expected context. The only usage clue is the implied 'when you need subtitle file contents'.

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