ass_set_script_info

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

With no annotations, the description carries the full burden and discloses several important behavioral traits: case- and space-insensitive key matching, preservation of existing spelling, conversion of the value via `str`, rejection of newlines, current-document defaulting, and insertion-before behavior. It does not cover permissions, reversibility, or overwrite semantics explicitly, but the behavioral context is substantially detailed.

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 front-loaded with the core action and then organized into Args and Returns sections. It is appropriately sized and information-dense, though the Returns section is partly redundant since an output schema exists, and the opening phrase is slightly awkward.

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?

Given no annotations, 0% schema coverage, and an output schema, the description provides strong parameter and behavioral detail. It also explains the return structure, which is helpful even though the output schema covers it. It stops short of explicitly stating overwrite behavior for existing keys and error cases, but it is largely complete for correct invocation.

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 does so thoroughly for all four parameters. It provides an example for `key`, explains matching rules and spelling preservation, constrains `value` to no newlines and `str` conversion, documents `doc_id` as optional/current-document, and clarifies `before` insertion behavior.

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 gives a specific verb and resource: setting/inserting/updating a `[Script Info]` key. It is clear enough to distinguish from sibling read/remove operations by implication, but it does not name any sibling or explicitly route between them. The phrasing 'reposition-free-update' is slightly awkward, though the intent is still understandable.

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?

The description explains how the `before` parameter behaves when a key is missing, but it does not state when to use this tool versus alternatives such as `ass_get_script_info` or `ass_remove_script_info`. There is no explicit when-to-use or when-not-to-use guidance, leaving tool selection mostly to inference from the name.

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