iaas_get_azure_storage_profiles

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond repeating "Get" and the raw endpoint URL — no pagination, no filtering behavior, no note about whether all Azure storage profiles or only those in a cloud account are returned.

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?

Three short lines, but the first two are near-duplicates ("Get Azure storage classes" / "Get all Azure storage classes") and the third is just an endpoint URL. It is front-loaded and not bloated, but includes redundant framing without adding substance.

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?

For a read-only list tool with full annotation coverage and a fully documented single param, the essentials are present. However, with no output schema, the agent gets no hint about what a storage profile object contains or whether the result includes associated cloud accounts, which would help selection.

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 100% with a single optional apiVersion parameter that is fully documented in the schema. The description doesn't mention apiVersion at all, but the schema carries that burden, so baseline 3 applies.

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 names a specific verb-and-resource pair ("Get all Azure storage classes") that tells the agent this is a list operation scoped to Azure storage profiles. It doesn't distinguish itself from siblings like iaas_get_azure_storage_profile (singular) or the generic iaas_get_storage_profiles, leaving the agent to infer the collection semantics.

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 versus the singular Azure profile getter or the provider-agnostic list. No prerequisites, filtering context, or alternatives are mentioned.

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