List Groups Storage

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

With no annotations, the description carries the full burden of behavioral disclosure, but 'Get Storage' only implies a read operation. It does not mention side effects, permissions, rate limits, or what kind of storage data is returned, leaving the agent with minimal behavioral understanding.

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 short, which is superficially concise, but this is under-specification rather than effective conciseness. It provides almost no useful content while every word is trivial.

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?

An output schema exists, so return value details are partially covered, but the description still omits essential context such as what 'storage' refers to, which group scope is involved, and how this differs from admin storage endpoints. The tool is not adequately specified for an agent to invoke it confidently.

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 description coverage is 0%, and the description adds no meaning to the single optional 'accept-language' parameter. The parameter is somewhat self-explanatory from its name, but the description does not compensate for the lack of schema documentation.

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 'Get Storage' is essentially a tautology of the tool name/title and provides no specific detail about what kind of storage listing this is or what it returns. It does not distinguish this from sibling tools such as list_admin_maintenance_storage, making the purpose unclear beyond the name itself.

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?

There is no guidance on when to use this tool versus alternatives. The description gives no context about scope, audience, or relationship to nearby storage-related tools, so an agent cannot determine when this is the right choice.

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