get_database_cluster

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

The description implies a read operation, but with no annotations, it fails to confirm idempotency, safety, or any side effects. No mention of output structure or rate limits.

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?

Extremely short, but lacks critical information. Concise at the expense of completeness. The single sentence does not earn its place given missing details.

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 presence of sibling tools, two required params, and no annotations or output schema, this description is insufficient for reliable selection and invocation. It provides almost no context beyond the resource name.

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?

With 0% schema description coverage, the description must compensate, but it provides zero information about the required parameters (namespace, name) or their meanings. The agent gains no insight beyond the parameter names.

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 it retrieves details of a specific database cluster, but does not differentiate from sibling tools like get_database_cluster_components or get_database_cluster_credentials. The verb 'Get details' is somewhat generic.

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 guidance on when to use this tool versus alternatives (e.g., get_database_cluster_components). No exclusions or prerequisites mentioned.

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