iaas_get_azure_cloud_accounts

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. The description contributes the organization-level scoping constraint, but says nothing about pagination defaults or what the response collection looks like, so it adds modest value beyond the annotations.

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 first two lines restate the same fact ('Get Azure cloud accounts' / 'Get all Azure cloud accounts within the current organization'), and the raw path 'GET /iaas/api/cloud-accounts-azure' is implementation noise already present in the annotation title. Front-loaded intent is fine, but a third of the text is redundant.

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, org-scoped list endpoint with complete schema coverage and full annotations, the description gives the agent enough to call it correctly. Only paging/return-shape detail is absent, and no output schema exists, which is a minor gap rather than a blocking one.

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% (top, skip, apiVersion each documented), so the baseline of 3 applies. The description adds no meaning about paging behavior or default record counts, so it neither compensates nor detracts.

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?

States a specific verb and resource ('Get all Azure cloud accounts') plus the scope ('within the current organization'), which separates it from the cross-provider iaas_get_cloud_accounts and the single-object iaas_get_azure_cloud_account. It never names those siblings explicitly, so differentiation must be inferred from the name.

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?

The org-scoped listing intent is implied, but there is no explicit when-to-use/when-not guidance and no reference to alternatives such as iaas_get_cloud_accounts (all providers) or iaas_get_azure_cloud_account (single account). An agent must infer routing from naming conventions alone.

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