ssh_estimate_transfer

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. It does not state what actions are performed, whether the estimate is a calculation or live test, what units are used, or what side effects (if any) occur. This is a complete lack of transparency.

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 one short sentence, but it is under-specified rather than concise. It does not earn its place because it provides almost no useful information. The brevity is not a virtue when the content is vacuous.

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 lack of output schema and annotations, and only a vague name to infer from, the description is grossly insufficient. It does not explain what the estimate is based on, what the return value represents, or any caveats. The tool is effectively unusable based on the description alone.

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 0% and the description does not mention the parameters 'operation' or 'file_size_bytes'. The tool adds no meaning to the input schema, failing to explain how these values affect the transfer time estimate.

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 'Estimate transfer time' is essentially a tautology of the tool name 'ssh_estimate_transfer' and does not specify what transfer is being estimated, whether it is for SSH uploads/downloads, or what the output represents. It lacks a specific verb+resource distinction from sibling tools.

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 is provided on when to use this tool versus alternatives. It does not mention any prerequisites, scenarios, or exclusions. The description offers no context for selecting this tool over similar SSH or transfer-related utilities.

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