Receive File

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

The annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the agent already knows this is a non-idempotent, non-destructive outward-facing operation. The description adds nothing: it does not say whether existing local files are overwritten, how fan-out across the group is handled, what happens on partial failure, or how parallel/max_threads affect behavior.

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 short and front-loaded, so it is not bloated, but the second sentence is boilerplate shared with the whole tm_inventory family and carries no tool-specific information. It is concise without being informative.

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 16-parameter file-transfer tool with no required parameters, no enum constraints, and a schema salted with run_command-only options, the description needed to say at minimum which parameters govern a receive_file call and what the source/target semantics are. It supplies none of that; even the existence of an output schema does not compensate for the missing operational contract.

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 100%, so the 16 parameters are documented in the schema itself and the baseline of 3 applies. The description contributes no additional parameter meaning, and notably several schema entries (host, preview, cmd) are scoped to "run_command only", leaving the agent to infer which of the 16 knobs actually matter for a receive-file call.

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 restates the tool name ("Receive file") and adds only a generic family tagline, "Bulk inventory operations against YAML host groups." It never says receive a file from which inventory host(s) to where locally, nor how this differs from the sibling tm_remote_receive_file or from tm_inventory_send_file. An agent can guess the general area but not the specific operation.

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?

There is no when-to-use guidance, no exclusion, and no mention of alternatives such as tm_remote_receive_file (single host) or tm_inventory_send_file (opposite direction). With 38 sibling tools in the same listing, the absence of any routing signal is a real gap.

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