account_clear

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

No annotations provided, but description explains that it resets in-memory subscription override and cached SDK clients, causing next operations to re-authenticate. This is transparent about behavioral effects, though could include caveats like potential need for user interaction.

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 concise sentences, front-loaded with the core action. Every sentence provides value with no wasted words.

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?

Tool is simple (no params), output schema exists, and description covers operation and effect. Context is complete given low complexity.

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?

No parameters exist; baseline score of 4 applies per rules since schema coverage is high (100%) and description adds no param details needed.

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?

Description clearly states it clears cached Azure credentials and subscription override, with a verb (clear) and resource, and distinguishes from siblings like account_get_access_token or account_show by mentioning 'similar to az account clear' and specifying the effect.

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?

Usage is implied clearly: when you need to reset cached credentials for re-authentication. However, no explicit when-not or alternative tools are mentioned, though the context makes it obvious.

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