set_upload_done

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that finalizing triggers post-upload hooks (notifications, contribution acceptance, etc.) and implies a mutating action. It could mention idempotency or error conditions, but it gives relevant side-effect context beyond what the name alone conveys.

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 the first stating the core purpose and the second providing usage context. It is front-loaded, direct, and contains no redundant or irrelevant information.

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?

For a one-parameter tool with no output schema, the description covers purpose, side effects, and when to call it. A minor gap is that it doesn't describe the return value or error behavior, but given the simplicity of the operation, this is not a significant deficiency.

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?

The schema description for the single 'id' parameter is 100% covered, stating it's the numeric Upload id (NOT the guid) returned by create_upload_session. The description adds no additional parameter detail beyond this, so baseline 3 applies.

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 action ('Finalize an upload session, marking it as complete') and distinguishes it from the sibling upload tools (create_upload_session, upload_file/upload_files) by positioning it as the finalization step. It also specifies the side effect (triggers post-upload hooks), leaving no ambiguity about its role.

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 explicitly says to call this after the last upload_file/upload_files in a batch opened with create_upload_session, providing clear sequencing guidance. It doesn't mention when not to use it or alternatives, but no alternative finalize tool exists, so the guidance is sufficient.

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