Connect Azure

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

The description is rich about security behavior and the expected user flow, but it presents the tool as returning a script for the user to run later, which implies a read-only informational operation. The annotations declare readOnlyHint=false, meaning the tool is not read-only, so the description contradicts the structured behavioral hint.

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 front-loaded with the key constraint (keeping the secret off the model) and then explains the why and the flow. It is somewhat verbose but every part supports the unusual security model, and the examples are compact.

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?

There is no output schema, so the description appropriately explains that the tool returns a Cloud Shell script and that the user must finish with `finops setup azure`. That is enough for an agent to route the user correctly, though it could mention prerequisites or what the script 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?

The tool has zero parameters, so the description does not need to explain parameter semantics. The baseline for no parameters applies, and nothing in the description misleads about inputs.

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 purpose: guiding Azure connection while keeping the service-principal secret off the model, and it explicitly distinguishes this flow from connect_aws and connect_gcp. It also says the tool returns a Cloud Shell script for the user to finish in their own terminal, so the tool's role is clear.

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?

It names the alternatives connect_aws and connect_gcp and explains why they are different: those read local credentials, while Azure requires a client secret that must not be pasted into the model. The examples further reinforce when to use it (connecting Azure or asking how to connect an Azure subscription).

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