Get Azure resource details

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

With four annotations (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false) already covering the safety and side-effect profile, the description adds genuinely useful behavior beyond them: 'Secret values are masked' warns the agent not to expect live credentials in the response, and the child-resource scope clarifies what 'any resource type' includes. No contradiction with annotations is present. It stops short of describing error behavior for nonexistent resources, but the masked-secrets disclosure is a meaningful value-add.

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?

Four sentences with zero waste: primary behavior first, then scope, then the critical caveat, then the sourcing hint. Each sentence carries distinct information and the most important facts are front-loaded ahead of the auxiliary guidance. This is appropriately sized for a two-parameter read-only tool.

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 low-complexity tool (2 params, 1 required, no nested objects), the description covers all invocation-relevant ground: what it returns and its field inventory (partially compensating for the absent output schema), scope boundaries, a response caveat, and how to obtain the one required parameter. The four annotations complete the safety picture. The only omission—error handling for missing resources—is minor and does not affect correct invocation.

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 both resourceId (including a full path example) and apiVersion (including default behavior) already documented, so the baseline is 3. The description contributes one extra parameter-level insight—that resourceId should be sourced from azure_find_resources—which helps the agent obtain the required argument correctly. That lifts it a notch above the baseline.

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 opens with a specific verb and resource: 'Returns the full Azure Resource Manager definition of one resource,' then enumerates the content (configuration, SKU, identity, networking, state). Explicitly noting it works for 'any resource type, including child resources such as deployment slots' distinguishes it from the resource-specific siblings like azure_aks_overview and azure_containerapp_overview. The 'one resource' scope cleanly separates it from the discovery tools azure_find_resources and azure_resource_graph_query.

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 description gives clear, actionable context: it is the generic full-definition lookup for any resource, and it explicitly directs the agent to 'Get the resource ID from azure_find_resources,' naming the exact sibling that supplies the required parameter. However, it never states when not to use it or that resource-specific overview tools exist as alternatives for deeper domain views, so it lacks explicit exclusions.

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