rollback

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose that rollback is a mutating and potentially disruptive operation, whether it is reversible, what happens to current traffic or replicas, or what permissions are required.

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, front-loaded sentence with no wasted text. It is appropriately sized for the tool's purpose.

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?

For a mutating deployment operation with no annotations and no output schema, the description is incomplete. It omits consequences, safety profile, and expected outcome, leaving the agent without enough context to invoke it confidently in risky scenarios.

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 100%, so the service and deploy_id parameters are already documented. The description mentions the optional deploy_id but adds no format, constraints, or behavior 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 states a specific verb and outcome: roll back a service to its previous version or a specified deploy_id. It clearly identifies the operation, though it does not explicitly distinguish it from siblings like restart, deploy, or promote_replica.

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?

It briefly explains the default and optional target, but gives no when-to-use guidance relative to alternatives such as restart or deploy. There are no prerequisites, exclusions, or conditions under which rollback is inappropriate.

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