create_replication_job

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

No annotations are provided, so the description carries the full burden. It discloses that 'type' currently only supports 'local', and includes parameter defaults. However, it does not mention authorization requirements or side effects like job scheduling behavior. Given the absence of annotations, it is fairly transparent but could be more explicit.

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 concise and well-structured with a brief introductory sentence followed by a bullet list of parameters. Every line provides useful information without unnecessary text.

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?

Given the tool complexity (7 parameters, 2 required) and the presence of an output schema, the description covers all parameters with meaningful explanations. It provides sufficient context for an AI agent to correctly invoke the tool.

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 add meaning. It does so effectively by specifying id format ('GUEST-JOBNUM'), target as 'target node', type restriction to 'local', schedule format ('systemd calendar'), and defaults for other parameters. This adds significant value beyond the schema.

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 clearly states 'Create a storage replication job' with a specific verb and resource. It distinguishes from sibling tools like 'create_backup_job' and 'delete_replication_job' by the unique resource type.

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 parameter details like id format and default schedule, but does not explicitly guide when to use this tool versus alternatives such as 'create_backup_job'. The usage context is implied by the resource name.

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