Отключить Яндекс Товары

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

Beyond the annotations (destructive, not read-only, not idempotent), the description discloses important behavioral details: it does not affect the environment variable token and does not revoke remote access, which must be done separately. This adds significant transparency about side effects and limitations.

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 concise, consisting of three clear sentences, each adding essential information. It is well-structured: first states the primary action, then clarifies what is not affected, and finally notes the remote persistence. No unnecessary 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?

The description provides complete context for the tool's behavior, including its scope (local token only) and the need for separate revocation. Since there is no output schema, return values are not a concern. The description fully covers the tool's operational context.

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 no parameters, so schema coverage is 100%. The description does not need to explain parameters, and the baseline for high coverage is 3. No additional parameter information is required.

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's function: deleting the saved Yandex Products token from disk. It distinguishes this tool from others by its specific action and title, making its purpose unambiguous.

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 provides useful usage context by explaining what it does (deletes local token) and what it does not do (doesn't touch env var, doesn't revoke remote access). It implicitly guides when to use it, though it doesn't explicitly state 'use this when you want to log out'. This is sufficient for most cases.

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