scp

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

The description states 'Copy', implying a write operation, which matches the annotation 'readOnlyHint: false'. However, it adds no additional behavioral context beyond what annotations already provide. Important details like whether overwrites occur silently, error handling, or authentication methods are missing.

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 sentence that efficiently conveys the core purpose without unnecessary words. Every part of the sentence adds value, making it concise and well-structured.

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's complexity (6 parameters, no output schema), the description is too brief. It fails to mention expected outputs, error states, or that the operation is bi-directional (upload/download). A more complete description would include success/error behavior and authentication requirements.

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?

All parameters have descriptions in the input schema (100% coverage), so the description adds no extra meaning. Baseline score of 3 is appropriate as the schema does the heavy lifting, but the description does not clarify parameter relationships or provide additional constraints.

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 'Copy files to or from a remote host using SFTP (SCP-like)' uses a specific verb ('Copy') and resource ('files to/from remote host') that clearly defines the tool's function. It differentiates from siblings like 'ssh' (interactive shell) or 'curl' (HTTP transfers) by specifying file transfer via SFTP.

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 (e.g., ssh, curl), nor does it mention prerequisites such as SSH access or authentication requirements. The agent is left without context for selecting or invoking the tool appropriately.

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