aad_reset_client

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

The description discloses the core behavior (reset cache, force re-authentication) but lacks details on side effects, required permissions, or whether ongoing sessions are affected. Since no annotations exist, the description carries the full burden and provides only moderate transparency.

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 a single, clear sentence that efficiently conveys the tool's action. No wasted words, and the key information is front-loaded.

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 the tool's simplicity (no parameters, a single action), the description is complete. The presence of an output schema eliminates the need to explain return values.

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 are no parameters, so the empty schema is fully covered. Per guidelines, with 0 parameters the baseline is 4. The description adds no additional parameter information, which is acceptable.

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 clearly states the tool resets a cached Azure AD client and forces re-authentication. This is specific and distinguishes it from sibling tools like aad_create_application or aad_list_users, which perform different operations.

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 implies usage when authentication issues occur or a fresh token is needed, but does not explicitly state when to use this tool versus alternatives. No guidance on prerequisites or exclusions.

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