iaas_get_gcp_storage_profiles

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds essentially nothing beyond restating the GET endpoint: no note on scoping (e.g. per cloud account), pagination, or result size – the bare "Get all" is the only extra hint.

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 line ("Get GCP storage classes") and second line ("Get all GCP storage classes") are near-duplicates, so one of the three lines is wasted.

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 endpoint with no output schema, the description should at least tell the agent what a returned storage profile represents and whether the list is tenant-wide or cloud-account scoped. Instead it is a raw endpoint stub, leaving the agent to infer both the return shape and the scope.

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?

Only one optional parameter (apiVersion) exists and the schema documents it at 100% coverage, so the baseline of 3 applies. The description adds no additional meaning about the parameter or its defaults.

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 verb+resource is identifiable as a list of GCP storage profiles, but the description calls them "storage classes" while the name, path, and sibling tools all use "storage profile" – an inconsistent term. It also makes no attempt to separate itself from the very close siblings iaas_get_gcp_storage_profile (singular), iaas_get_storage_profiles, or iaas_get_aws_storage_profiles.

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 statement of when to use this versus the singular get or the multi-cloud iaas_get_storage_profiles. The only usage signal is the implied "get all", which is not framed as guidance or an exclusion.

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