Connect Azure

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

The description discloses non-obvious behavior: the tool does not accept or transmit the secret, it returns a Cloud Shell script, and the user must complete the connection in their own terminal with the secret encrypted into a local vault. This goes well beyond the generic annotations, and nothing contradicts readOnlyHint/destructiveHint.

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 core purpose, then uses a focused rationale and examples. Each sentence contributes either the security constraint, the comparison to alternatives, or the concrete command to run; no filler.

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 zero parameters and no output schema, the description fully covers what the tool returns (a Cloud Shell script), what the user must do next, why the tool exists, and example invocation phrasings. It is complete for safe 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?

The tool has zero parameters, and the description explains why: Azure credentials cannot be safely auto-detected, and a secret would have to be pasted into chat/tool args, which nable intentionally avoids. This adds crucial semantic meaning to the empty input 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?

Clearly states it is a guide for connecting Azure, with the specific security constraint of keeping the service-principal secret off the model. It distinguishes itself from connect_aws and connect_gcp by explaining their local-credential behavior vs Azure's need for a client secret.

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?

Explicitly contrasts with connect_aws and connect_gcp: those read machine-local credentials and require no sensitive pasting, while Azure requires a client secret that must not enter the chat. It also directs the user to finish with `finops setup azure` in their own terminal, making the usage path clear.

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