Список кластеров баз данных

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

The description describes a read-only operation ('Returns a list'), but the annotation readOnlyHint=false contradicts this. This is a direct contradiction, making the behavioral semantics confusing. The annotation should be true for a listing operation.

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 two sentences long, front-loads the purpose, and includes the API path as a useful reference. No unnecessary 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?

For a simple listing tool with optional pagination, the description provides purpose and usage. However, the contradiction with annotations creates uncertainty about the tool's behavior. It also doesn't mention return structure, but that's not required given no output schema. Overall, adequate but with a notable inconsistency.

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?

The input schema covers both parameters fully with descriptions (100% coverage). The description adds no additional parameter semantics, but the schema already provides sufficient detail. Baseline 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 'Returns a list of database clusters of the account' with a specific verb and resource, and includes the API endpoint. It distinguishes from sibling tools like list_all_project_clusters or list_database_instances by specifying database clusters.

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 provides a clear usage context: 'Use before operations on a cluster to get its ID.' This tells the agent when to invoke the tool. It does not mention alternative tools or exclusions, but the guidance is actionable.

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