list_storage_accounts

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

The tool is a list operation, which implies read-only behavior, but the description does not explicitly confirm this or disclose any other behavioral traits like authorization requirements, rate limits, or error handling. Given no annotations, the agent must infer safety from the verb.

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 very short and front-loaded with the purpose. It includes a dedicated line for the parameter, which is efficient. However, it could benefit from a brief note on output or scope.

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?

The description covers the basic functionality and required parameter but lacks details on output (though output schema exists), whether accounts are from all subscriptions, or pagination. For a simple list, it is adequate but not comprehensive.

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 provides a title 'Resource Group' and type string. The description adds 'Resource group name', which is only slightly more specific. With only one parameter and high schema clarity, the added value is minimal.

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 verb 'List' and the resource 'storage accounts', with scope 'in a resource group', making it specific and distinguishable from sibling tools like 'list_resources' (broader) and 'get_storage_status' (status).

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?

No guidance is provided on when to use this tool versus alternatives, nor are any exclusions or context given. The description merely states what it does without usage hints.

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