Azure sign-in and subscriptions

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

Annotations already provide a thorough safety profile: readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds no significant operational behavior beyond what annotations cover, aside from reinforcing that subscriptions are readable. No contradiction exists.

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-load the output contents and then provide practical call-first guidance. There is no filler, and every phrase earns its place.

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 zero-parameter, read-only context tool, the description sufficiently explains what it returns, when to call it, and why it matters. There is no output schema, but the listed information—identity, tenant, and readable subscriptions—is enough for an agent to decide whether to invoke the tool.

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 takes zero parameters, so there are no parameter semantics for the description to clarify; per the zero-parameter baseline this is a 4. The description's mention of subscription IDs is context for the tool's output, not parameter documentation.

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 uses a specific verb and resource: it 'Shows' the signed-in Azure identity, tenant, and readable subscriptions. This clearly distinguishes it from sibling tools, which focus on logs, metrics, and resource data rather than account context.

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 explicit trigger conditions: 'Call this first when you need a subscription ID, or when another tool reports an authentication or permission problem.' It lacks an explicit 'when not to use' or named alternatives, but the guidance is unambiguous and actionable.

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