empire_download

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the tool is read-only, requires specific permissions, or modifies state. Without annotations, the description carries the full burden, but it only states the basic action. No side effects or constraints are mentioned.

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, direct sentence with no unnecessary words. It efficiently conveys the core purpose. No extraneous information.

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 simplicity (2 required params, no output schema, no annotations), the description is minimally adequate. However, it omits useful context such as where the file is saved locally or whether the path is absolute/relative. Completeness is acceptable for a low-complexity tool but could be improved.

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 coverage is 100% with descriptions for both parameters (agent_id, remote_path). The description does not add more meaning beyond the schema, so it meets the baseline of 3. It could provide examples or format hints but does not.

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 action ('Download a file') and the resource ('from an Empire agent'). It distinguishes from siblings like empire_upload (upload file) and empire_shell (execute commands). However, it could be more specific about the source (e.g., 'remote file from the agent's filesystem').

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 explicit guidance on when to use this tool versus alternatives. The description does not mention scenarios, prerequisites, or when not to use it. Sibling tools like empire_shell, empire_upload, and empire_task_result cover related but distinct actions, but no comparison is provided.

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