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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description usefully adds that the operation executes with no human approval. What it omits is consequential: whether turning it off tears down existing per-PR Environments, and what the response contains. For a toggle that may shave PR environments, that gap matters.

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?

Two short sentences, front-loaded with the action and scope, with no filler. The no-approval note is the only extra and it earns its place.

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?

The schema is rich and there is no output schema to explain, so the structural side is covered. Still, the description leaves the effect of disabling undefined and says nothing about return values or the expect_revision conflict behavior, which an agent needs before flipping this switch.

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%, so all five parameters are already self-documenting, including the boolean semantics of 'enabled' and the meaning of expect_revision. The description adds no parameter-level detail beyond 'built from this Environment', so the baseline 3 applies.

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?

States a specific verb pair (turn on/off) and a specific resource (an Environment per GitHub pull request) that is clearly different from environment_setup, environment_protect, and environment_remove. It is not fully crisp: 'Environment per GitHub pull request, built from this Environment' requires knowledge of the product's Environment concept, and the tool's core effect is described only in toggle terms.

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?

'built from this Environment' implies the prerequisite that an existing Environment must exist, and 'This call asks no human' signals the toggle is unapproved/automatic. However, no sibling is named and no when-not/alternative is given (e.g. environment_protect vs this), so the agent must infer selection on its own.

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