ssh_estimate_transfer

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

With no annotations, description must fully disclose behavioral traits. It only states estimation with no details on method, inputs (e.g., need for active session), or side effects. Insufficient for safe usage.

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?

Description is brief and front-loaded with purpose and args. Could be more structured (e.g., bullet-like), but no unnecessary words. Efficient.

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?

Despite having an output schema, the description only mentions 'Estimated transfer time and recommendations' without specifics. Lacks context on accuracy, network assumptions, or how the estimate is derived. Underwhelming for a tool needing trust.

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?

Description adds meaning beyond schema: clarifies that 'operation' can be 'upload' or 'download' (schema lacks enums). Explains 'file_size_bytes' is in bytes. This offsets the 0% schema description coverage.

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?

Description clearly states the tool estimates file transfer time over SSH, a distinct function among siblings. The verb 'estimate' and resource are specific and differentiate it from other SSH tools like ssh_session_command or ssh_sessions.

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?

No guidance on when to use this tool vs alternatives. No mention of prerequisites or conditions, leaving the agent to infer applicability without context.

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