Переменные контента бота

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

Beyond annotations (write, non-destructive), the description discloses that existing keys are updated, new ones created, and secret-marked values are not shown back. It also specifies key character constraints, providing valuable behavioral details.

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 compact sentences, front-loaded with the main action, and every sentence adds essential information. No fluff or redundant repetition of schema fields.

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 the schema richness and annotations, the description fully complements the structured data. It covers core behavior, key format, secret handling, and update semantics, making the tool's purpose and constraints complete for an 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 schema already covers all parameters (100% coverage), but the description adds key format constraints (Latin, digits, underscore, dot) not present in the schema. It also reinforces the behavior of the 'secret' field, adding meaning beyond the schema.

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 states a specific verb ('Задаёт' - sets) and resource ('переменные' - variables for bot script texts), with concrete examples (prices, addresses, links). It clearly distinguishes this tool from siblings like bots_save or bots_control by focusing on content variables.

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 clear context through examples ('цены, адреса, ссылки') and explains the update/create behavior, implying when to use it. It does not explicitly name alternatives or exclude cases, but given the unique sibling scope, the usage is evident.

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