Создание S3-хранилища

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

Annotations already mark non-readOnly/openWorld, and the description adds that it returns access_key and secret_key — useful behavior not present in the annotations or output schema. It doesn't discuss billing or side effects, but openWorldHint partially covers that.

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 concise sentences: the first states the operation, the second covers required fields, alternatives, and return value. No fluff or redundancy.

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 create operation with 7 params and no output schema, this description covers the essential purpose, input alternatives, and output credentials. The optional project_id/description are left to the schema, which is acceptable since schema descriptions are complete.

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 baseline is 3. The description adds the crucial XOR rule ('ЛИБО preset_id, ЛИБО configurator_id + configurator_disk_mb') and clarifies that configurator_disk_mb is needed when using configurator_id, which the schema marks as merely 'опц.'.

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 opens with 'Создаёт новое S3-хранилище' — a clear verb+resource statement. It unambiguously creates a bucket and differentiates this from the many other create_* sibling tools by specifying S3 storage.

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 clearly states required inputs and the exclusive-or requirement between preset_id and configurator_id+configurator_disk_mb. It doesn't explicitly mention alternatives or when-not-to-use, but the context is sufficient for selecting this tool over others.

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