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

Beyond the structural hints (read-only), the description adds crucial behavioral context about the return value, such as including 'its version, the end mark the plan adds, what is still to complete,' and details the specific handling of the 'since' parameter.

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 dense, managing several pieces of information—scope, comparison to siblings, parameter function, and return content—within a tight space, though the prose is slightly narrative.

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 the lack of an output schema, the description provides a very complete picture of the returned data, listing the entire film, version, completion status, and missing pictures.

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?

While schema coverage is 100%, the description adds semantic value by specifying that the 'since' parameter should be answered with 'unchanged' when the state is still, clarifying its role as a state-check mechanism.

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 tool clearly defines its function as drawing a film specifically for 'Cutscene's window.' It successfully distinguishes itself from the broader 'read' functionality by explicitly suggesting the alternative, get_film.

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 provides explicit rules for usage, stating it is 'For Cutscene's window only' and directing the agent to prefer get_film for general reading.

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