iaas_get_storage_profile

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

Annotations already state readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the HTTP path: it does not say what a storage profile represents, whether unknown ids error or return empty, or whether provider-specific fields vary.

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 short and front-loaded, but the first two lines are near-duplicates ('Get storage class' / 'Get storage class with a given id') and the third is just the raw endpoint path. Minimal, though almost no sentence adds information the agent could not infer.

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 simple read-only single-resource fetch with no output schema and fully documented parameters, this is adequate. It is thin on the one thing that matters here: differentiating a generic storage profile from the many provider-specific storage profile getters in the sibling list.

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% and both parameters are documented, so the baseline of 3 applies. The description adds nothing beyond what the schema already says about 'id' (the path identifier) and 'apiVersion', but it does not need to.

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 ('Get storage class with a given id'), so an agent knows this retrieves a single storage profile by identifier. It does not distinguish from siblings, notably iaas_get_storage_profiles (the list form) or the provider-specific variants like iaas_get_aws_storage_profile, which is a real ambiguity in this crowded namespace.

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 about when to use this versus iaas_get_storage_profiles, iaas_get_storage_profile_associations, or the per-provider getters. The only implicit usage signal is the required 'id' parameter, and the description offers no exclusions or prerequisites.

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