ssh_mkdir

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only says 'create directory' and omits any details about parent creation (despite a 'parents' parameter), timeout behavior, error handling, or side effects. The agent gets no warning about mutation or remote side effects.

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 short sentence, which is concise but under-specified for a tool with four parameters. It is front-loaded and easy to read, but it lacks the structural detail needed for a tool with options like 'parents' and 'timeout'.

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?

There is no output schema and no annotations, and the description provides only the most basic action. Missing information includes return values, the effect of the 'parents' flag, timeout semantics, and whether the operation is reversible or requires specific privileges. The tool is effectively a stub description.

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 any parameter meanings, including remote_path, parents, timeout, or host. The description adds no value beyond the schema field names, leaving the agent to guess what 'parents' or 'timeout' control.

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 the tool creates a directory on a remote host, which is a specific verb+resource. It clearly distinguishes from siblings like ssh_exec or ssh_remove, though it does not explicitly name alternatives. The purpose is unambiguous despite the lack of additional context.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or scenarios where another sibling tool would be more appropriate. This is a pure purpose statement without usage context.

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