finalize_file

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

Annotations only provide non-read-only and non-destructive hints. The description adds behavioral details: triggers flow assignment and function/type tracking checks. This goes beyond the annotations and gives the agent insight into side effects, though it could mention reversibility or permissions.

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 sentences with no filler, front-loading the primary action and then listing side effects. Every sentence serves a purpose.

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 5 parameters, no output schema, and annotations describing safety, the description covers the main function and side effects. It lacks details on error conditions or prerequisites, but is adequate for a mutation tool.

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 100%, so each parameter has a description. The tool description does not add any additional meaning or context for the parameters beyond what is in the schema, meeting the baseline expectation.

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 'mark' (equivalently 'finalize') the resource 'a reserved file' and specifies the context 'after writing it to disk'. It distinguishes from siblings like finalize_files (plural) and finalize_function by focusing on a singular file resource.

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 usage after writing a reserved file to disk, but does not explicitly state when not to use it or compare to alternatives like reserve_file or finalize_files. This provides some context but lacks clear guidance.

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