Push Environment

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

Annotations already declare destructiveHint=true, so the added value must come from additional context. The description does add that the operation returns an operation_id, indicating an asynchronous task, but it does not explicitly warn about data loss on the target or state required permissions.

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 that states the action, provides an illustrative example, and notes the return value. There is no wasted 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?

With 8 parameters and no output schema, the description still provides the essential operational fact that it returns an operation_id, enabling status polling. Destructiveness is covered by annotations. The only minor gap is not explicitly stating that the target environment is overwritten, though this is implied by 'push' and the destructive hint.

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 100%, with all eight parameters having descriptions. The description itself adds no further parameter semantics, so it meets the baseline for schema-covered tools.

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 the specific verb 'Push' with a clear resource ('one environment to another') and an example ('staging to live') that differentiates it from sibling clone/backup/restore operations. It clearly defines the operation's direction and scope.

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 the primary use case with an example but does not explicitly say when to choose this over alternatives like clone, restore, or delete, nor does it state any exclusions. With relevant siblings present, this leaves ambiguity.

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