jms_sftp_mkdir

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

No annotations are provided, so the description carries the full burden. It discloses one behavioral aspect (optional parent creation) but does not mention behaviors like error handling when the directory exists, permissions, or side effects. For a mutation tool without annotations, this is a significant gap.

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 one concise sentence with no fluff. It front-loads the core action and includes the key optional behavior. It is appropriately sized for the tool's apparent simplicity.

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 presence of an output schema, return values are covered, but the description still lacks essential context such as prerequisites for use, handling of existing directories, and parameter semantics. With three parameters and zero schema description coverage, the description is too sparse to be considered complete.

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 only hints at the 'parents' boolean via 'optionally creating missing parents' but does not clarify the meaning of 'path' (e.g., relative vs absolute) or 'session_handle' (e.g., how to obtain it). The description adds minimal value beyond the bare schema.

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 states a specific action ('Create a remote directory') with a clear resource target and an optional behavior (creating missing parents). It clearly distinguishes from sibling tools like jms_sftp_list or jms_sftp_delete, as no other tool creates directories.

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 about when to use this tool vs alternatives, prerequisites (e.g., needing an active SFTP session), or situations where mkdir would be inappropriate. The single sentence does not provide any context for decision-making.

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