zadig_service_update_yaml

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

With no annotations provided, the description carries the behavioral disclosure burden. It does state that the operation is mutating and requires confirm=true, which is useful safety information. But it does not explain side effects, whether the replacement is destructive, what permissions are needed, or what happens if confirm is false.

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 only two short sentences with no filler. The confirm requirement is front-loaded and important, though 'This is mutating' is somewhat redundant with 'Replace'.

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 six parameters, no annotations, and 0% schema coverage, the description is too sparse to be complete. It covers the mutation warning and confirm prerequisite but omits parameter semantics, usage context, and any operational detail beyond replacing YAML.

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%, so the description must compensate, but it only clarifies the confirm parameter. It does not explain the meaning of yaml, service_name, service_type, production, or project_key, leaving most of the six parameters semantically undefined.

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 opens with 'Replace service YAML', a specific verb and resource that clearly identifies the operation. This distinguishes it from sibling service tools like set_variable, set_image, and update_variables, which target different aspects of a service.

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 implies this tool is for replacing a service's YAML definition, and it states a necessary precondition ('requires confirm=true'). However, it gives no explicit guidance on when to choose this tool over alternatives, such as update_variables or set_image, and no mention of when not to use it.

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