create_sftp_connection

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it offers none. It does not state whether credentials are validated, whether duplicate names are allowed, what authentication is required, or what side effects occur beyond creating the resource. This is a significant gap for a mutation tool.

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 the action verb first and no redundant phrasing. Every word earns its place, making it appropriately sized and front-loaded.

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?

With no output schema and zero required parameters, the description leaves the agent without context about the result of the operation (e.g., what is returned, whether the connection is usable immediately, or if there are constraints like unique names). It is under-specified for a tool that creates a resource and accepts multiple credentials.

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 input schema covers all six parameters with clear descriptions (e.g., 'SFTP host', 'Connection name'), so schema_description_coverage is 100%. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate.

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 'Create a new SFTP connection' uses a specific verb ('create') and clearly identifies the resource ('SFTP connection'). It distinguishes this tool from its siblings (list/get/update/delete/test_sftp_connection) by signaling a create operation.

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, nor does it mention any prerequisites. It does not explicitly exclude other connection-related operations like test_sftp_connection or update_sftp_connection, leaving usage to be inferred solely from the verb 'create'.

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