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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral fact — a mode restriction to interactive user-scoped sessions — but says nothing about what happens outside that mode, whether the list can be empty, or how it relates to revocation. Adequate but thin beyond what structured fields provide.

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, zero waste, and the scope/return content is front-loaded ahead of the availability constraint. Every sentence carries information an agent needs.

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 and the parenthetical field list are already covered; the description needn't repeat them. For a simple zero-required-param read tool with full annotation coverage, it is essentially complete — only the lack of sibling routing slightly lowers it.

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?

There is a single optional parameter (context_id) with 100% schema description coverage, so the schema already handles the semantics. The description says nothing about context_id or its fallback behavior, which is acceptable at this coverage level but adds no value.

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 (returns active Azure sessions) plus the enumerable output fields (tenant IDs, usernames, expiry, last used), and scopes to 'the current user'. That scoping implicitly separates it from check_azure_session_for_account and check_azure_session_for_tenant, but those siblings are never named, so differentiation is inferential rather than explicit.

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 availability constraint ('only available in user-scoped mode (web chat)') is useful context for choosing this tool. However, it offers no guidance on when to prefer this over azure_user_session_revoke, check_azure_session_for_account, or check_azure_session_for_tenant — usage is implied only by the phrase 'current user'.

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