Забыть доступ на этой машине

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

The description discloses that the token is not revoked server-side, a key behavior beyond the annotations. It clarifies that the action is local and non-reversible through this tool, significantly aiding user expectations.

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 two-sentence description is concise and front-loaded, stating the core action first and adding essential nuance in the second sentence without redundancy.

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, output-less tool, the description fully covers functionality, side effects, and the path to full revocation. It leaves no critical questions unanswered.

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?

With zero parameters, the baseline of 4 applies as there are no parameter details to elaborate on, and the description need not compensate for schema gaps.

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 erases a saved token locally, using the verb 'erase' and specifying the resource ('saved token') and scope ('on this machine'). It also distinguishes itself by noting the token remains valid, setting it apart from revocation tools.

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?

It implies usage when the user wants to log out on this machine only, and explicitly directs to the panel for full revocation. While it doesn't name sibling tools, the alternative path is clearly outlined, providing adequate when-to-use and when-not-to-use guidance.

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