ass_set_play_res

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

No annotations are provided, so the description carries the full burden. It discloses the return payload, but that duplicates the existing output schema rather than adding behavioral context. It does not state permissions, whether the change is undoable, or what doc_id=null selects.

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?

Two short sentences, front-loaded with the operation. The second sentence spends space restating return fields that the output schema already documents, which is minor waste.

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 an output schema present, return values need not be explained, yet they are the only extra content. For a mutation tool with no annotations and 0% parameter coverage, the description omits the effect of PlayRes on rendering, document targeting, and reversibility.

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, and it largely does not. It maps x/y to PlayResX/PlayResY but gives no units, valid ranges, or interaction between the two values, and doc_id is entirely unexplained.

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 (Set) and a specific resource (PlayResX/PlayResY), which is a unique setting not touched by any sibling tool. It is distinguishable from siblings like ass_set_wrap_style or ass_set_script_info, though it assumes the agent knows what PlayRes means in an ASS file.

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 when-to-use guidance, no prerequisites, no alternatives named. It never says whether a document must be open, whether doc_id defaults to the active document, or when changing play resolution is appropriate (e.g., before scaling drawings).

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