Получение инстанса кластера

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

The description describes a read operation ('returns information'), but the annotation readOnlyHint=false contradicts this, suggesting the tool may modify state. This is a serious inconsistency, so behavioral transparency is not disclosed accurately.

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?

Single, front-loaded sentence in Russian that conveys the action and endpoint without waste.

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?

Simple tool with two required parameters and no output schema. Description provides the endpoint and resource but does not detail return shape, usage context, or contrasts with siblings. The contradiction with readOnlyHint also reduces completeness.

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% with parameter descriptions. The tool description adds no additional semantic meaning beyond what the schema provides, so the baseline score of 3 applies.

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 it returns information about a database instance in a cluster, with the verb 'возвращает' and the resource. It distinguishes from list_database_instances by targeting a specific instance, and includes the full API endpoint.

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?

No explicit when-to-use or exclusion of alternatives is provided. The context implies it is for fetching details of a single instance, but it does not contrast with list_database_instances or mention prerequisites.

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