ssh_git_pull

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions authentication methods but fails to disclose critical behaviors such as potential merge conflicts, the need for git to be installed on the remote, or any output/error handling. This lack of transparency could lead to misuse.

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 concise with two sentences, the first defining the core action and the second adding authentication support. It is front-loaded and avoids unnecessary detail, though it could be slightly more structured (e.g., bullet points).

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 has 9 parameters, no output schema, and no annotations, the description covers the main action and authentication but omits important context like error scenarios, prerequisites (git on remote), and behavior of optional parameters. Adequate but not fully 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 100%, so baseline is 3. The description adds useful context on authentication options (private key vs password) but does not elaborate on other parameters like branch, port, or passphrase beyond what the schema already provides. No additional semantic value for those.

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 clearly states the specific action: SSH into a remote host and run git pull in a specified repo directory. The name and description together precisely define the tool's purpose, distinguishing it from more general SSH command execution tools like ssh_run_command.

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 implies usage for updating a git repository via SSH but provides no explicit guidance on when to use this tool versus siblings (e.g., for other commands use ssh_run_command). No exclusions or alternatives are mentioned.

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