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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, and the description adds behavior beyond them: it discloses the two possible outcomes, including a device-code payload on failure, which signals the call may initiate an interactive auth flow. It does not mention caching or token lifetime, but the success/failure contract is clear.

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 short sentences, front-loaded with the purpose and the preflight framing, followed by the return contract. 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?

An output schema exists, so return values need not be spelled out in detail, and the description still summarizes them. The main gap is not linking the azure_login_required outcome to a follow-up login tool, but the definition is otherwise sufficient to call it correctly.

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% and both parameters are optional and documented in the schema, so baseline 3 applies. The description adds nothing about how azure_tenant_id defaults or what omitting context_id implies beyond what the schema already says.

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?

States a specific verb and resource: 'validates Azure auth for the tenant directory.' The 'for the tenant' scope distinguishes it from the account-level sibling check_azure_session_for_account, though that sibling is never named explicitly.

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?

'Internal preflight' implies it should run before Azure operations against a tenant, which is useful contextual framing. However, it never states when to choose this over check_azure_session_for_account or azure_user_session_status, nor what the caller should do after receiving azure_login_required.

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