snapshot_azure

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, giving a solid safety profile. The description adds that it performs a live scan and produces blueprint JSON, but fails to explain the write side effect (e.g., whether a blueprint is created or stored) and any required permissions. With annotations present, this partial addition warrants a 3.

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 single sentence is front-loaded and contains no filler. However, for a tool with four parameters and no schema descriptions, a slightly more structured explanation could be appropriate, so it is not perfectly sized.

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?

Given four parameters (two required, 0% schema description coverage), a non-read-only annotation profile, and an output schema, the description is substantially incomplete. It omits parameter meanings, authentication requirements, and any clarification of the mutation’s effect, leaving the agent with too many gaps to call the tool confidently.

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 0% for all four parameters, so the schema offers no meaning for account_id, region, filter, or exclude. The description only indirectly hints at the region parameter ('one Azure region') and gives no information on the other three, leaving parameter usage largely unexplained.

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 ('Scan'), resource ('one Azure region'), output ('blueprint JSON'), and method ('Cloudcraft live-scan'). It clearly distinguishes the tool from generic list/get tools, though it does not explicitly contrast with the sibling snapshot_aws or clarify whether the JSON is returned or persisted.

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 use this tool versus alternatives like snapshot_aws, list_azure_accounts, or create_blueprint. The description gives no prerequisites, exclusions, or context for selection.

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