arvan_vod_list_subtitles

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

Description aligns with readOnlyHint and destructiveHint annotations. Adds 'List subtitles' which implies a read operation, but no additional behavioral details beyond annotations (e.g., pagination, limits). No contradiction.

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?

Single sentence is concise, conveying basic purpose. But it lacks additional useful details; every sentence earns its place, but the description is too brief for a tool with no parameter descriptions and no output 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?

Despite having one parameter and no output schema, the description does not explain what information is listed (e.g., subtitle languages, status, metadata). Missing context on error handling or response format. For a list tool, more completeness is expected.

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 coverage is 0%: parameter video_id has no description. Description only implies video_id is the video identifier but provides no detail on format, constraints, or examples. Description does not compensate for lack of schema descriptions.

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?

Description clearly states the verb 'List' and resource 'subtitles for a video'. Distinguishes from sibling VOD list tools by specifying subtitles. However, could be more specific about what is returned (e.g., subtitle IDs, languages).

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?

No guidance on when to use this tool vs alternatives like arvan_vod_get_subtitle or other list tools. No exclusions or preconditions mentioned.

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