azure_get_resource_details

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get detailed configuration and properties' without revealing whether the tool is read-only, what authentication or permissions are needed, or any rate limits. This lack of context could mislead an agent into expecting modifications or missing required 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 description is extremely concise: one sentence for the core purpose and one sentence for use cases. It is well-structured and front-loaded, with no wasted words.

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?

Despite having 6 parameters and no output schema, the description is minimally adequate. It mentions what the tool returns ('detailed configuration and properties') but does not specify the format or structure of the output. Given the complexity of Azure resources and the lack of output schema, more detail on return values would be beneficial.

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 coverage is 100%, so the baseline is 3. The description does not add significant meaning beyond the schema; it only includes an example of resource provider values already listed in the schema. The parameter descriptions in the schema are self-explanatory, so the description offers limited additional value.

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 clearly states the tool's action ('Get detailed configuration and properties') and the resource type ('specific Azure resource'). It also provides concrete use cases ('analyzing security settings, network configs, encryption status') which differentiates it from sibling tools that are more specialized analysis tools.

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 implies usage for general resource detail retrieval ('Useful for analyzing...'), which distinguishes it from the siblings that focus on specific analysis (e.g., azure_analyze_nsg_rules). However, it does not explicitly state when not to use this tool or mention alternative tools for more specific needs.

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