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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real context beyond that by disclosing what the response contains — the environment's phase and last error — which helps an agent decide whether a response is actionable.

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, with the capability stated first and the REST path second. The path is somewhat redundant given the schema parameters, but it is compact and not distracting.

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?

A simple single-resource read with full annotation coverage, complete parameter documentation, and no output schema. Mentioning phase and last error gives enough of the return shape; only minor gaps (error behavior for missing environments) remain.

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 three required identifiers are documented in the schema; the description adds no further meaning about their format or relationships. This is the expected baseline when the schema carries the parameter burden.

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 and resource with scope ('Read one environment') and names two fields it returns (phase, last error). The singular 'one' implicitly separates it from environment.list and the mutating siblings (create/delete/suspend/resume), though no sibling is named explicitly.

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?

Usage is only implied: fetching details for a single known environment ID. There is no explicit guidance on when to use this instead of environment.list, or on prerequisites such as needing the environment to exist or permissions required.

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