geck_backup_plugin

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the copy operation and destination, which implies a non-destructive read from Data and a write to the backup directory, but it does not mention overwrite behavior, whether the backup directory is created automatically, or what happens if the plugin is missing or already backed up.

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, tightly worded sentence with no filler. It front-loads the action and states source and destination economically, and every part of the sentence adds useful 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?

While the core operation is clear, the description is incomplete for a tool with three parameters, two of which are undocumented, and no annotations. There is no mention of when to use the optional parameters, what backup behavior to expect, or how this relates to the larger backup/transaction workflow implied by sibling tools.

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 0%, and the description only implicitly clarifies plugin_name by referring to the .esm/.esp being copied. The optional label and game_dir parameters are completely unexplained, leaving the agent without enough information to decide whether to set them or what values they expect.

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 a specific verb ('Copy') and names both the source ('Data') and destination ('MCP backup directory'), and it targets a specific resource type (.esm or .esp). This clearly distinguishes it from sibling tools like geck_save_active_plugin or geck_esp_patch_ref_position, which perform different operations.

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 guidance on when to use this tool versus alternatives, nor any stated prerequisites or exclusions. It does not explain whether this should be run before edits, as part of a transaction, or instead of geck_save_active_plugin. The agent is left to infer the appropriate context.

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