list_stateful_nodes

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

No annotations are provided, so the description carries the full burden. It explains that default output is compact summaries and verbose returns full configurations. However, it does not disclose pagination behavior, rate limits, or permissions. The added context about output modes is valuable but incomplete.

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 extremely concise at 4 lines, front-loaded with the core purpose, and includes parameter details in a clear, bullet-like structure. Every sentence adds value.

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 simplicity (2 parameters, list operation) and the presence of an output schema, the description covers purpose, parameters, and usage well. Missing details like region scope or pagination, but these are minor for a straightforward list tool.

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 0%, so the description must provide parameter meaning. It explains account_id's default (env var) and verbose's purpose and use cases. This adds significant value beyond the bare 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 clearly states 'List all Stateful Nodes (Managed Instances) in an AWS account,' specifying the resource and action. It distinguishes from siblings like 'get_stateful_node' and 'list_stateful_nodes_azure' by adding 'AWS account' to scope.

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?

Provides guidance on when to use the verbose parameter ('Use when analyzing node settings, troubleshooting, or comparing configs') and mentions the default account_id from env var. However, it does not explicitly state when to use alternatives (e.g., get_stateful_node for a single node) or when not to use this tool.

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