set_attribute

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

No annotations are provided, so the description must convey behavioral traits. It only briefly mentions changing an attribute, lacking details on overwrite behavior, permission requirements, or error handling. The description does not disclose side effects or operational context.

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, using a single sentence in Russian. No fluff or unnecessary information. While concise and efficient, it lacks a structured format (e.g., bullet points) but earns its place.

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 tool has 4 required parameters and no output schema or annotations, the description provides minimal context about return values or error scenarios. It is adequate for a simple tool but leaves behavioral gaps.

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?

Input schema has 100% description coverage, with each parameter described. The tool description adds no further meaning to the parameters beyond what the schema already provides. Baseline score of 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 tool changes one attribute of an object, specified as 'один реквизит объекта'. The name 'set_attribute' directly matches this purpose. It distinguishes from sibling tools like update_object by emphasizing single-attribute changes and mass point edits.

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 implies use for batch single-attribute edits ('массовых точечных правок'), but does not explicitly state when to use versus alternatives like update_object. No direct exclusions or alternative tool references are given.

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