Запуск и остановка бота

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

Annotations already state readOnlyHint=false and destructiveHint=false, so the agent knows this mutates bot state. The description adds useful behavioral nuance: startup automatically syncs the menu, while a separate sync is required after editing commands on a live bot. This goes beyond what structured data provides.

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 compact sentences: the first enumerates the actions, the second explains the only important conditional nuance. There is no filler, no restating of the schema, and the key context is front-loaded.

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 simple three-parameter tool with no output schema, this description covers the main actions and the sync nuance well. A brief note on the effect of stop/restart on a running bot would add completeness, but the current text is sufficient for correct selection and invocation.

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 all parameters. The description reinforces the meaning of the action enum by explaining the sync_commands edge case, but it does not add extra detail about the bot or case parameters. 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 starts with a specific set of actions and resource: 'Запускает, останавливает или перезапускает бота, а также отправляет меню команд'. This clearly distinguishes bots_control from sibling tools like bots_save or bots_journal by naming the runtime-control responsibility.

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 explicit guidance about when the sync_commands action is needed: after editing commands on an already running bot, because startup already performs synchronization. It does not name sibling alternatives, but the provided context is unambiguous for the listed actions.

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