Показать токен бота

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

Beyond the annotations, the description adds crucial behavioral context: the token grants full control over the bot, and the tool should be used only on explicit user request. This meaningfully expands on destructiveHint=true and explains why the operation is sensitive.

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?

Two sentences, zero filler. The first sentence states the primary function; the second delivers essential security guidance. The most important operational caution is placed up front.

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 two-parameter tool with no output schema, the description covers the action, the sensitive nature of the result, and the required user-consent condition. It is complete enough for safe invocation, though it does not detail output formatting or explicitly rule out token rotation.

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?

Schema coverage is 100%, so the schema already documents both bot and case parameters. The description adds no parameter-specific meaning beyond the operation itself, so baseline 3 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 operation: 'Возвращает токен бота в открытом виде' — a specific verb, resource, and even the output form. It is recognizable as distinct from siblings like bots_get, but it does not explicitly name or differentiate against any sibling, so it falls short of a 5.

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 gives an explicit usage condition: request the token only if the user directly asks, and do not repeat it unnecessarily. It provides clear context and a strong exclusion rule, though it does not mention alternatives or broader when-not-to-use scenarios.

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