save_job_files

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

Annotations only declare openWorldHint=true, so the description carries the real burden and does so well: it discloses that results are deleted from BitPull's store and survive only on the local machine, an irreversible data-movement consequence an agent must know before calling. It stops short of covering failure behavior when the folder is unauthorised or whether existing files are overwritten.

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 short sentences, zero filler, with the data-location consequence front-loaded right after the action. Every clause carries information an agent needs.

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 simple two-parameter tool the critical data-loss semantics are covered, but there is no output schema and the description says nothing about what is returned, what happens if the folder is not authorised, or whether a partial or failed save leaves results in limbo.

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 0% with no parameter descriptions, so the description must compensate. It conveys that jobId refers to a finished job and that folder must be an authorised location, but gives no format or path expectations for 'folder' or constraint detail for the UUID jobId.

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 names a specific verb and resource: saving the large results of a finished job into a folder. That scope is distinct enough from siblings such as fetch_files or job_status, though it never explicitly contrasts itself with any of them.

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?

Usage is implied rather than stated: the job must be 'finished' and the folder must be 'authorised', which hints at prerequisites (likely bitpull_authorize_folder). There is no explicit when-not guidance or named alternative for retrieving results some other way.

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