list_stateful_nodes

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

Discloses default compact summaries and full configs with verbose, indicating read-only operation. No annotations exist, so description carries burden; lacks details on pagination, ordering, or limits.

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?

Efficient, front-loaded main purpose, uses bullet-style formatting for args with no redundant information.

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?

Complete for a list tool with output schema: covers both parameters, default behavior, and two output modes. No missing critical details given low complexity.

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?

Adds significant meaning beyond schema: explains account_id default behavior (env var) and verbose intent, with 0% schema description coverage. Both parameters well-documented.

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 the action (list) and resource (Stateful Nodes/Managed Instances in AWS account), and the name distinguishes it from siblings like get_stateful_node and list_stateful_nodes_azure.

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 verbose mode ('analyzing node settings, troubleshooting, comparing configs') but does not explicitly exclude other similar list tools or state when not to use it.

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