Create replication job

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

Annotations already indicate this is not read-only (readOnlyHint=false) and not idempotent (idempotentHint=false). The description adds the requirement of matching storage but does not discuss side effects like network usage or whether creation triggers immediate replication. With openWorldHint=true, more behavioral context would be beneficial.

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 extremely concise: one sentence for the primary action and one for a critical requirement. Every word serves a purpose, and there is no fluff. It is appropriately front-loaded.

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 complexity (8 parameters, 4 required, no output schema), the description is incomplete. It omits details about the schedule format, the difference between local and remote types, error handling (e.g., duplicate job IDs), return values, and immediate effects. The agent would need to infer too much from the schema alone.

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 63%, but the tool description provides no additional explanation for any parameters beyond what is in the schema. For example, the schedule format is only hinted at in the schema's example, and the type enum (local/remote) is not explained. The description adds no value for parameter understanding.

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 the verb 'Create' and the resource 'ZFS replication job' for a VM or container, distinguishing it from siblings like update_replication_job and delete_replication_job. It also includes a key requirement (target storage must match), which aids in correct usage.

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 a prerequisite ('Target must have a matching storage') but lacks explicit guidance on when to use this tool versus alternatives like update_replication_job. It does not mention that the job is scheduled or that the same job ID should not be duplicated. The context is adequate but not comprehensive.

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