Close Scene

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

No annotations exist, so the description must fully disclose behavior. It mentions marking complete and writing change, but omits reversibility, prerequisites, and side effects on related data—important for a state-changing operation.

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 one concise sentence with clear, front-loaded phrases. Every word contributes value and no redundancy exists.

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 annotations, no output schema, and a state-changing operation, the description is too sparse. It lacks critical context about consequences (e.g., whether closing is irreversible), effects on chapter/project status, and expected return value.

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 50%, with change and foreshadow_ids described. The description clarifies that change is the result to write and that foreshadow linking is optional, but it does not add significant meaning beyond the schema for scene_id and project_id, which are self-explanatory.

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 tool marks a scene complete, writes the change, and optionally associates foreshadowing. The specific verb and resource (close scene) distinguish it from sibling tools like update_scene.

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 implies use for finalizing a scene, but does not explicitly state when to use it vs alternatives or when not to use it. No exclusions or alternative tools are named.

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