iaas_get_fabric_azure_storage_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 elsewhere. The description adds nothing behavioral beyond restating the name and raw GET path — no mention of pagination behavior, default page size, filterable fields, or what happens when no Azure fabric is onboarded.

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 text is short but redundant: the first line and second line say effectively the same thing ("Get fabric Azure storage accounts" / "Get all fabric Azure storage accounts"), and the raw endpoint duplicates the annotation title. It is front-loaded and not bloated, but two of three lines fail to add information.

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 a fully documented schema and strong annotations, the essentials are present. What is missing is domain context an agent would need to disambiguate the resource — what a "fabric Azure storage account" represents versus an Azure storage profile, and whether the result set is paginated — with no output schema to fall back on.

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%, with top, skip, count, filter, select, and apiVersion each documented in the schema itself, so the baseline is 3. The description contributes no additional meaning about how filter predicates are formed or how select interacts with the response, but it does not need to given full coverage.

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 ("Get all fabric Azure storage accounts") and the underlying endpoint, so the agent knows this is a collection read of Azure fabric storage accounts. It does not, however, distinguish itself from the near-identical sibling iaas_get_fabric_azure_storage_account (singular) or from iaas_get_azure_storage_profiles, leaving ambiguity about list-vs-single-record and fabric-vs-profile 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 choose this tool over its siblings, nor any stated preconditions (e.g., that the Azure cloud account must be registered). The word "all" hints at a list operation but nothing explicit routes the agent between this and iaas_get_fabric_azure_storage_account or iaas_get_azure_storage_profiles.

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