ssh_insert_lines

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

Discloses operational detail (uses sed, only new content sent) but does not address error handling, permission requirements, or behavior for invalid line numbers. No annotations provided, so description carries full burden.

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?

Concise and well-structured: brief operational summary followed by clear parameter list. No unnecessary words.

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?

Covers mechanism and parameters well. Lacks return value or error behavior, but for a simple insertion tool, this is adequate given parameter thoroughness.

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 coverage is 0%, but description explains all parameters: path, after_line (1-based, 0 for beginning), content, host (optional with default). Adds crucial context beyond 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?

Clearly states verb (insert), resource (file on remote server), and insertion point (after a specific line number). Distinguishes from sibling tools like ssh_append_file and ssh_replace_lines.

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?

Hints at efficiency (no full-file transfer) but does not explicitly guide when to use vs alternatives or mention when not to use. Lacks clear differentiation from siblings.

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