Отключить Аудитории

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false, idempotentHint=true), the description adds critical context: it only deletes the token from disk, does not affect the env var token, and the server-side access remains active. It also mentions how to revoke access via Yandex ID, which is essential for the agent to understand the tool's full effects. No contradiction with annotations.

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?

Three sentences, each with a distinct purpose: what it deletes, what it doesn't touch, and what remains active. No fluff, all information is directly relevant. The structure is logical and front-loaded with the primary action.

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 no parameters and no output schema, the description covers all necessary aspects: action, scope, exceptions, and consequences. It fully explains the tool's behavior and implications, leaving no gaps for the agent.

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 tool has zero parameters and the schema coverage is 100% (there are no parameters to document). The description doesn't need to elaborate on parameters, so a baseline of 4 is appropriate.

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 verb+resource: 'Deletes the saved Audiences token from disk'. It distinguishes itself from login-related siblings (start_login, finish_login, auth_status) by specifying the exact action and its scope. No ambiguity about what the tool does.

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 you want to log out by removing the token from disk). It also provides important guidance about the env var token not being touched and how to handle it, which is crucial for correct usage. It doesn't explicitly name alternatives, but there are no direct logout siblings, so it's adequate.

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