exploit_copy

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'copy' without explaining side effects like overwriting files, creating directories, whether the destination is local or remote, or any permissions required.

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, brief sentence with no redundant words, making it easy to read and front-loaded. However, it is arguably under-specified, which limits the value of its conciseness.

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?

With no annotations, no output schema, and 0% schema coverage, the description needs to provide more context. It leaves critical questions unanswered, such as where the exploit comes from, whether the destination is on the local machine or a target, and what happens after execution.

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 0%, so the description must explain the parameters. It maps 'exploit' to edb_id and 'destination' to destination, but it does not specify the expected format of edb_id (e.g., numeric ID) or clarify that destination is a filesystem path with a default of /tmp.

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 the specific verb 'copy' and identifies a resource ('exploit') and destination, which clearly distinguishes it from sibling tools like exploit_search and exploit_details. However, it does not specify the source of the exploit (e.g., exploit-db), leaving some ambiguity about what 'exploit' refers to.

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?

The description provides no guidance on when to use this tool versus alternatives, such as target_upload_file or kali_upload. There is no mention of prerequisites, typical use cases, or exclusions.

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