Backup

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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, destructive=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether a backup overwrites existing archives, where it runs, whether it requires credentials, or how long it may take on large trees.

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?

It is very short, but the second sentence is generic filler that adds no usable information, and the useful signal (that this backs up files) is not expanded at all. Brevity here is under-specification rather than efficiency.

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?

A complex, 24-parameter, open-world mutation tool with no required params and no output explanation needed (output schema exists) still requires the description to state what gets backed up, from where, to where, and under what auth — none of which is present.

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 24 parameters are documented individually and the baseline is 3. However, the description does nothing to disambiguate the mixed-operation parameter set (backup_paths, backup_dest, compression, incremental vs. content_search/watch/diff params) — a real missed opportunity given how confusing the schema is.

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 title/name is restated ("Backup (tm_files)") and the only elaboration, "Advanced file operations on remote hosts," describes the whole tm_file_* family rather than this tool. An agent cannot tell from this text how backup differs from tm_file_recursive_ops or tm_remote_send_file.

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 statement, no mention of alternatives such as tm_remote_send_file for a one-off transfer, and no stated prerequisites (SSH connectivity, remote_host/username requirements). The agent must infer everything from the name.

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