target_download_file

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the operation name. It does not mention checksum verification, session type behavior, authentication requirements, side effects, or return format. This is a significant transparency gap.

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 extremely short and front-loaded, with no wasted words. However, it is under-specified for a tool with four parameters and no annotations, making it less helpful than a concise but informative description would be.

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 (4 params, no annotations, no output schema), the description is incomplete. It does not explain return values, behavior across session types, or how it relates to sibling download/upload tools, leaving significant gaps for an agent to act reliably.

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 offers no parameter information. It does not explain the meaning of session_id, remote_path, session_type, or verify_checksum, all of which are left to the reader to infer from the schema alone.

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 uses a clear verb ('Download') and resource ('target session'), and the presence of the sibling tool 'target_upload_file' helps distinguish it as the download counterpart. However, it does not explicitly mention 'file' or remote path, leaving slight ambiguity about what is being downloaded.

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 instead of alternatives like ssh_session_download_content, reverse_shell_download_content, or kali_download. The description gives no context about session types or exclusions.

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