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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description earns credit for clarifying the blast radius of the default path (omitting azure_tenant_id revokes all sessions), which is the single most important behavioral fact for this destructive call. It stops short of saying whether revocation is reversible or whether refresh tokens/other devices are affected.

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 filler, with the destructive default scope stated up front right after the core action.

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 no explanation, and annotations carry the safety profile. However, for a destructive auth operation the description omits what exactly is destroyed (device sessions, tokens), any prerequisite that the user must be signed in, and whether the action can be undone — gaps an agent would want before invoking 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?

Schema coverage is 100%, so both parameters are already documented, including 'omit to revoke all' which the description merely restates. The description adds the useful framing that the target is the current user's sessions, but supplies no extra detail on context_id handling or tenant ID format.

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 (revoke Azure session(s)) plus the scope qualifier 'for the current user'. It is distinguishable from the read-only sibling azure_user_session_status, though it never names any sibling 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?

The conditional sentence tells the agent what happens when azure_tenant_id is supplied vs omitted, which implies usage but does not say when to prefer this tool over alternatives such as azure_user_session_status (check first) or azure_user_login_start (re-authenticate). No prerequisites or exclusions are stated.

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