execute_code

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

The description discloses that code runs in privileged mode, a critical behavioral trait. It also specifies that the result must be in a variable named 'Результат'. However, it does not elaborate on potential side effects or security implications beyond privilege mention.

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 very concise with three sentences, each adding essential information: purpose, behavior, and usage guidance. No wasted 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?

While the description covers the basics for a code execution tool, it could be more complete by warning about irreversible actions or suggesting failure handling. Given no output schema, it provides adequate context for 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?

With 100% schema coverage, the schema already describes the 'code' parameter as '1C code text'. The description adds meaning by explaining that code runs in privileged mode and that the result should be assigned to a specific variable, which guides usage.

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 it executes arbitrary 1C code, a powerful tool. It distinguishes itself by indicating it is used when other tools do not fit, which aligns with the sibling context.

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?

Explicitly advises using the tool only when other instruments are not suitable, providing clear guidance on appropriate use cases.

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