iaas_get_fabric_azure_storage_account

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only the REST endpoint path, which gives modest extra context but nothing on return shape, pagination, or permissions.

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 same statement is repeated across three lines ('Get fabric Azure storage account' twice, then the endpoint path) before any distinguishing detail. The repetition costs space without adding information, and the one useful qualifier ('with a given id') is buried on line two.

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 by-id tool with complete schema coverage and strong annotations, the description is minimally adequate, but it omits any pointer to the listing sibling and says nothing about what the response contains.

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%, so all three parameters (id, select, apiVersion) are already documented. The description adds no meaning beyond the schema, so the baseline 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?

States a specific verb ('Get') and resource ('fabric Azure storage account') and adds 'with a given id', which distinguishes a single-record fetch from enumeration. It does not name the plural sibling iaas_get_fabric_azure_storage_accounts, so full sibling differentiation is left to the agent.

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?

Usage is only implied: an agent can infer this is the by-id lookup and the plural sibling is for listing, but the description never states when to use this versus iaas_get_fabric_azure_storage_accounts or any prerequisites.

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