jms_sftp_list

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states 'List' which implies read-only, but it doesn't mention permissions, error handling, path validation, or what the output contains. The description adds minimal behavioral context beyond the action itself.

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, concise sentence with no wasted words. It is front-loaded with the primary action. However, it is so brief that it borders on under-specification, though for a simple list operation it is still efficient.

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 the tool's placement among many SFTP session management siblings, the description lacks critical context such as requiring an active session, how to obtain one, or what the output format is (though an output schema exists). It is not complete enough for an agent to confidently invoke it in a real workflow.

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%, so the description must compensate. It does not explain 'path' or 'session_handle' at all. While parameter names are somewhat self-explanatory, 'session_handle' requires context about acquiring an SFTP session, which is missing.

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 'List one absolute remote directory path' clearly states the action (list) and the resource (a remote directory path). It specifies absolute and remote, which adds precision. However, it does not explicitly say 'contents' or differentiate itself from sibling tools like jms_sftp_stat, though 'list' vs 'stat' is a natural distinction.

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. It doesn't mention that it requires an active SFTP session or how it relates to sibling tools like jms_sftp_stat or jms_sftp_mkdir. The description provides no context for selection.

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