list_stateful_nodes_azure

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

With no annotations, the description must fully disclose behavioral traits. It explains that the tool returns compact summaries by default and full configurations when verbose is true, and lists example fields in verbose mode. However, it does not mention permissions, rate limits, pagination, or other potential side effects. The behavioral description is adequate but not comprehensive.

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: two sentences for the main purpose plus a brief parameter list. Every sentence provides necessary information without redundancy. The structure front-loads the core functionality, then details the optional verbose mode and parameters. No wasted words.

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 existence of an output schema, the description does not need to detail return values but covers the key distinction between compact and verbose output. It lists example fields for verbose mode (compute, networking, persistence). It lacks notes on pagination or data volume, but for a list tool with output schema, the description is mostly complete.

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?

The input schema has 0% description coverage, so the description must compensate. It includes an 'Args' section explaining both parameters: 'account_id' as the Azure account ID and 'verbose' with usage notes and default value. This adds significant meaning beyond the schema's titles and defaults, satisfying the parameter documentation fully.

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 Azure Stateful Nodes in an account,' specifying the verb, resource, and scope. It distinguishes from sibling tools by including 'Azure' in the name and mentioning 'Stateful Nodes.' However, it does not explicitly contrast with siblings like 'list_stateful_nodes' (for other clouds) or 'get_stateful_node_azure' (single node).

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 provides guidance on when to use the 'verbose' parameter ('Use when analyzing node settings, troubleshooting, or comparing configs'), but it does not indicate when to use this tool versus alternative tools such as 'list_stateful_nodes' (for other clouds) or 'get_stateful_node_azure' (for a single node). No when-not or exclusion criteria are given.

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