jms_sftp_download

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

No annotations are provided, so the description carries the full transparency burden. It discloses the key overwrite behavior ('replacing a local file requires overwrite=true'), but omits other important traits like error handling, permission requirements, or partial-download behavior, leaving the agent under-informed.

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 a single, front-loaded sentence with a clear verb and a necessary caveat. Every word contributes, and there is no filler or redundant repetition of schema details.

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?

Although the tool is relatively simple and an output schema exists, the description lacks session context and only partially covers behavioral details. It is minimally viable but does not fully round out the operational picture for an agent selecting the 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?

The schema has 0% parameter descriptions, so the description must compensate. It adds meaning by mapping 'remote file' to remote_path, 'local file' to local_path, and overwrite to replacement logic, but it leaves session_handle entirely unexplained and does not specify path formats or defaults beyond overwrite's existence.

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 explicitly states 'Download a remote file' with a specific verb and resource, which clearly distinguishes this tool from sibling SFTP operations like upload, list, and delete. The overwrite caveat further clarifies its scope.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites such as an active SFTP session from jms_acquire_sftp_session, and no exclusions. The overwrite note is a behavioral condition, not usage guidance.

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