List Environment Nodes

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

Discloses pagination behavior, default limits (100 or 25 with detail=true), and response structure. Adds context beyond annotations (readOnlyHint, openWorldHint, etc.) without contradiction.

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?

Well-structured and mostly concise, but the argument list in the description partially duplicates schema properties. However, the pagination warning and alternative tool mention add significant value without excessive verbosity.

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?

Given the tool's complexity with pagination and optional detail, the description covers return values, default behaviors, and alternative tool. Output schema exists, so return values need less explanation, but the description still provides necessary context.

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 coverage is 100%, but description adds value by stating default values for limit (100 or 25 when detail=true) and explaining usage of startingFrom and orderBy, which are not fully detailed in schema.

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 states 'List nodes deployed in a Coalesce environment' with a specific verb and resource, and distinguishes from sibling get_environment_node by advising to use ID lookup when the node is known.

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?

Explicitly explains pagination: if hasMore is true, must page to avoid undercounting. Also recommends get_environment_node as an alternative when the node is known, providing clear when-to-use guidance.

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