environment_get

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

The annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the result includes publish state, which is useful beyond the annotation, but it does not disclose other behavioral aspects such as error cases or whether the metadata is a summary or full representation.

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, focused sentence that states the action, target, and a key piece of returned information. There is no filler or redundant restatement of the tool name.

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 simple read-only get operation with two fully described parameters and safety annotations, the description is mostly complete. The only notable gap is that it does not clarify how this differs from environment_get_definition, but the 'publish state' mention provides some differentiation.

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 both parameters are already documented with basic meaning. The description reinforces that these identify the 'specific environment,' but it adds no additional semantic detail such as ID format, required permissions, or parameter relationships.

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 a specific verb and resource: 'Get metadata of a specific environment.' The phrase 'including its publish state' adds useful detail and helps distinguish this from environment_list and environment_get_definition, though it does not explicitly name those siblings.

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 use when you need metadata for one specific environment, since it says 'specific environment' and requires both workspaceId and environmentId. However, it gives no explicit guidance about when to use environment_list, environment_get_definition, or other environment-related tools instead.

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