auth_clear

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

With no annotations, the description must disclose behavioral traits; it states the core action and its consequence. However, it does not mention whether the operation is reversible, whether it affects all sessions or tokens, or any prerequisites, leaving some ambiguity for a mutation tool.

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?

A single sentence containing exactly the necessary information, front-loaded with the verb and object. No filler or repetition.

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?

For a parameterless, void-style operation, the description captures the action and its primary effect. It does not explicitly mention return values, but the absence of an output schema and the simplicity of the operation make this acceptable.

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?

The schema has zero parameters, so there is nothing for the description to add. The description indirectly identifies the affected resource (authentication credentials), which is sufficient given the empty schema.

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 uses the specific verb 'Clears' with resource 'authentication credentials' and states the consequence 'forcing re-login on next request.' This clearly distinguishes it from the sibling auth_refreshToken, which performs a different action.

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 when to use it (when credentials must be discarded and re-authentication is required), but it does not explicitly mention alternatives or exclusions. There is no guidance contrasting with auth_refreshToken, leaving the agent to infer the choice from the verb 'clear.'

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