execute_azure_cli_command

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

With no annotations, the description carries full burden. It lacks disclosure of side effects, permissions, error handling, return format, or synchronization behavior. Only mentions command prefix and policy, which is minimal.

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?

Two sentences, front-loaded, no fluff. However, conciseness sacrifices completeness for a tool that executes arbitrary commands.

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 tool that executes arbitrary CLI commands with no output schema, the description is notably incomplete. It omits details on success/error responses, timeouts, how the execution policy works, and comparisons with sibling tool graph_command.

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 the schema already documents the parameter. The description adds the constraint that commands must begin with 'az', but this is partially redundant since the schema implies CLI commands. No significant additional semantics beyond schema.

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 verb 'execute' and the resource 'Azure CLI command'. It distinguishes from the sibling tool 'graph_command' by specifying the command prefix 'az', indicating Azure CLI focus.

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?

Provides some guidance ('commands must begin with az', 'subject to execution policy') but does not explicitly specify when to use this tool versus alternatives like graph_command, nor does it provide exclusion criteria.

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