download

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

With no annotations, the description carries the full burden of disclosing behavior. It does not mention potential side effects (e.g., overwriting existing local files), error conditions, or access requirements. The 'Returns' line is vague and adds no operational detail.

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 and uses a clear Args/Returns structure, but it is thin and the Returns section is uninformative ('Dictionary containing download status information'). It is not bloated, yet it under-delivers on substance.

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?

The tool has no output schema and no annotations, and the description does not explain what the returned dictionary contains, how to verify success, or how this tool relates to 'upload'. While the tool is simple, the missing context leaves the agent uncertain about invocation and result handling.

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%, so the description must compensate. However, it merely restates parameter names with generic descriptors ('Session ID', 'Remote file path', 'Local file path') that add little beyond the schema's own titles. No constraints, formats, or relationships are explained.

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 states 'Download file from SSH server' with clear verb and resource. The Args section clarifies the direction (remote to local) via 'remote_path' and 'local_path', distinguishing it from the sibling 'upload' tool.

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. There is no mention of prerequisites (e.g., active session), nor any exclusion or comparison with the sibling 'upload' tool.

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