Создание инстанса в кластере

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description's 'creates' is consistent with a mutation operation. The description adds the endpoint but does not disclose additional behavioral traits such as prerequisites, cost implications, or expected response. This meets the lower bar set by annotations.

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 consists of a single, front-loaded sentence that directly states the action, resource, and endpoint. There is no unnecessary information, making it highly concise and easy to parse.

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 tool with 3 fully documented parameters, clear annotations, and no output schema, the description provides sufficient purpose and context ('inside the cluster'). Minor gaps include not explicitly stating that the cluster must exist or describing the expected response, but these are not critical 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?

Schema description coverage is 100%, with each parameter clearly described in the schema (e.g., 'ОБЯЗАТЕЛЬНОЕ ПОЛЕ - название инстанса базы данных'). The description itself adds no parameter-level details beyond the schema, aligning with the baseline for high coverage.

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?

Description clearly states 'Создаёт новый инстанс (БД) внутри кластера' and provides the exact API endpoint (`POST /api/v1/databases/{db_cluster_id}/instances`). This distinguishes it from sibling tools like create_database and create_database_admin by specifying the resource and scope.

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 endpoint and the phrase 'внутри кластера' imply that an existing cluster is required, but the description does not explicitly state when to use this tool over alternatives like create_database or list_database_instances. There is no when-not-to-use guidance or mention of alternative tools.

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