arvan_vod_get_subtitle

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

Annotations declare readOnlyHint=true and destructiveHint=false, which inform the agent about safety. The description adds no additional behavioral context beyond what the annotations already provide, such as return value details or authentication requirements.

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 a single sentence and front-loaded, which is concise. However, it is minimal and lacks detail, making it adequate but not optimally informative.

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 no output schema and simple parameters, the description could explain what a subtitle is or what the tool returns (e.g., metadata). It fails to provide sufficient context for an agent to understand the tool's role within the VOD system, especially when sibling tools like list and create exist.

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?

The schema has 0% description coverage for the single required parameter 'subtitle_id', and the description does not provide any additional meaning beyond what the schema already indicates. The phrase 'by id' is implied by the parameter name and does not clarify format, source, or constraints.

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 clearly states the verb 'Get' and the resource 'subtitle by id', making the purpose clear. However, it does not differentiate from sibling tools like arvan_vod_get_audio or arvan_vod_get_channel, which follow the same pattern.

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 is provided on when to use this tool versus alternatives such as arvan_vod_list_subtitles or arvan_vod_delete_subtitle. The description lacks context about prerequisites or use cases.

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