jms_sftp_rename

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

With no annotations, the description carries the burden of behavioral disclosure. It adds the 'without overwriting' constraint, which is valuable, but does not disclose other behavioral traits such as behavior when the target exists (error vs. no-op), permission requirements, or support for directories.

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 sentence that is concise and front-loaded, with no wasted words. It effectively communicates the core purpose and a key constraint.

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 rename operation, the description is adequate but not fully complete. It does not mention whether it works on files and directories, nor what happens if the target already exists. The existence of an output schema mitigates the need to describe return values, but more operational context would improve completeness.

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 description coverage is 0%, and the description does not elaborate on the parameters. While 'path' and 'new_name' are somewhat self-explanatory, 'session_handle' is not mentioned, and no additional meaning is added beyond the parameter names.

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 ('Rename'), the resource ('remote entry'), and a key constraint ('without overwriting an existing sibling'). It distinguishes itself from sibling operations like delete, upload, and download.

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 for renaming remote entries but does not explicitly state when to prefer this over alternatives or provide exclusion criteria. The context of sibling tools makes the purpose evident, but no direct guidance is given.

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