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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile needs no repetition. The description's only added behavioral signal is that only 'visible' environments are returned, which is meaningful but not defined, and it says nothing about result volume or ordering.

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?

A single sentence with the verb and scope front-loaded and the optional filters trailing behind 'optionally'. There is no filler and nothing an agent must read past to get the core meaning.

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, unparameterized list tool with strong read-only annotations and no output schema, the definition covers what is needed to invoke it correctly. Its only real gap is that the 0%-documented string filters leave the caller uncertain what values to supply.

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 0%, so the description must carry the burden, and it does map all four filters by name ('orientation', 'movement', 'template', 'part') onto orientation, backgroundMovement, templateId, and partId. It does not explain what values are acceptable, and since orientation and backgroundMovement are free-form strings with no enums, an agent must guess the valid vocabulary.

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 ('List') plus the resource ('environments') and adds a scope qualifier ('visible') and the optional filter dimensions. It is clearly distinguishable from singular siblings like get_environment or get_default_environment, though it never explicitly names those alternatives.

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 word 'optionally' implies filters are not required, which is useful context, and 'visible' hints that hidden environments are excluded. However, there is no guidance on when to choose this over get_environment or get_default_environment, nor on how many results to expect.

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