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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with that. Beyond the annotations it adds real context: the content is bot-specific ('для этого бота'), so results vary by messenger, and it surfaces builder limitations ('что конструктор не умеет') that an agent would otherwise discover only through failed saves. With no output schema, it also broadly signals what comes back.

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, no filler. The content inventory is front-loaded so the agent knows immediately what it will get, and the second sentence is a single actionable instruction tied to chatbot.save.

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 single-parameter, read-only reference tool with no output schema, the description is nearly complete: it says what sections the reference covers and when to consult it. It stops short of indicating the return shape (plain text/markdown vs. structured steps), which would matter for an agent planning to parse the rules rather than read them.

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 description coverage is 100% and the single botId parameter is thoroughly documented in the schema, including where to obtain it (chatbots.list). The description only reinforces per-bot scoping with 'для этого бота' and adds no syntax or sourcing detail beyond the schema, so the baseline of 3 applies.

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 enumerates exactly what the tool returns for a given bot: step types, how to reference steps and variables, button/text limits for its messenger, unsupported features, and a sample scenario. That is a precise resource definition, though the verb is implicit (it never says 'returns'/'gets'). It also separates itself from chatbot.save by framing itself as the prerequisite reference.

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 gives an explicit trigger condition: call it before assembling or editing a scenario for chatbot.save, naming the sibling tool it feeds into. There is no explicit when-not guidance (e.g., that it is unnecessary for read-only inspection or for already-valid scenarios), but the routing intent is unambiguous.

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