env_push

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

No annotations are provided, so the description carries the responsibility for behavioral disclosure. It does well by stating direction, connection reuse, path format behavior, automatic creation of missing parent directories, recursive behavior, and credential requirements. It leaves overwrite semantics unspecified, which is a minor but real gap for a copy operation.

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?

Three sentences, each with distinct operational content, and the core action is front-loaded. It is efficient overall, though it slightly repeats details already present in the schema parameter descriptions.

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?

For a file-transfer tool with full schema coverage and an output schema present, the description covers the action, direction, path semantics, recursive behavior, parent directory creation, and credentials. Nothing critical for calling the tool correctly appears to be missing.

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?

The input schema already documents all four parameters at 100% coverage, including host/guest path semantics and recursive meaning. The description mostly restates this per-parameter information rather than adding new parameter-specific value, though it does add tool-level context about the connection and credentials.

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 opening verb phrase 'Copy a file or directory from this host into an environment' clearly identifies the action, resource, and direction. The reference to the same connection env_exec uses also differentiates it from sibling tools such as env_pull or env_exec itself, making the tool's role unambiguous.

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 clear contextual guidance: it explains host vs guest paths, forward-slash conventions, the need for recursive when copying directories, and the shared credential requirement with env_exec. It does not explicitly name alternative tools or say when not to use this tool, so it stops short of full exclusion guidance.

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