iaas_create_azure_storage_profile

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond restating the POST endpoint, which is already echoed in the annotation title — it does not mention that creation is non-idempotent (so retries may duplicate profiles), that an Azure cloud account is required, or what the response contains.

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?

It is a single front-loaded sentence plus an endpoint line — no padding. The endpoint line is somewhat redundant with the annotation title, which keeps it from a 5.

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 create operation with a rich nested schema and no output schema, the description is minimally adequate: the agent knows what to call and what to pass. It omits what is created on success (an ID to reuse?), the non-idempotent retry hazard, and any dependency on an existing Azure cloud account, which are the gaps an agent would actually need filled.

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 100% and the nested body object documents every field (name, regionId, diskType, caching, encryption, tags), so the schema carries the full burden. The description adds no interpretation of required fields or of the apiVersion parameter, so the baseline of 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 states a specific verb and resource ('Create Azure storage class'), which is clearly distinguishable from siblings such as iaas_create_aws_storage_profile and iaas_create_gcp_storage_profile via the provider qualifier. It does not, however, explicitly contrast itself with iaas_create_storage_profile (generic) or iaas_update_azure_storage_profile, leaving that inference to the reader.

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 the generic storage-profile create or the AWS/GCP variants, nor on prerequisites such as a registered Azure cloud account. The only context is the raw endpoint line, which does not help an agent choose between alternatives.

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