Revoke Authorization

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

The description discloses key behavioral traits: 'Clears stored tokens and stops any running authorization server; user must re-authorize afterward.' This informs the agent of destructive effects and required re-authorization. No annotations exist, so the description carries full burden.

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 two sentences, with the first sentence front-loading the primary usage condition. Every sentence adds value, no fluff.

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 zero parameters and the presence of an output schema (though not shown), the description covers when to use, behavior, and consequences thoroughly. It is complete for the tool's simplicity.

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 zero parameters, and schema coverage is 100%. The description adds context about the tool's purpose and effect beyond the empty schema. Baseline is 4 for no parameters.

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 action: 'revoke, reset, clear, or remove Dida365 authorization/tokens'. It specifies the verb and resource, and distinguishes from sibling tools by contrasting with token refresh and generic OAuth logout.

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?

Explicitly states 'Use ONLY when the user explicitly requests...' and provides specific scenarios (log out, revoke, reset, clear, remove, or cancel pending authorization). It also includes negative guidance: 'Do NOT call for token refresh, generic OAuth logout of other services, or routine task operations.'

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