ambari_clusters_getclusters

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, pagination behavior, or performance implications. The schema includes pagination parameters, but the description fails to mention that the response is paged or that it is a safe read operation. This leaves the agent without critical behavioral context.

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 a single sentence, which is concise but under-specified for a tool with 5 parameters. It does not front-load key information or provide structure. It is not verbose, but it could be expanded with minimal additional context to be more helpful.

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 complexity (5 parameters, no output schema), the description is too minimal. It lacks information about return format, default behavior, and usage patterns. The agent cannot fully understand how to invoke the tool correctly or interpret the response based solely on the description.

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 has 100% coverage with descriptions for all 5 parameters. The tool description adds no additional meaning beyond the schema, so it adds no value. The baseline score 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 'Returns all clusters' clearly states the verb (Returns) and resource (all clusters). It is concise and unambiguous, though it does not explicitly differentiate from the sibling tool 'ambari_clusters_getcluster' which retrieves a single cluster. The purpose is clear but could be improved by specifying it lists all 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?

There is no guidance on when to use this tool versus alternatives, such as the sibling 'getcluster' for a specific cluster. No context is provided about prerequisites or scenarios. The description lacks any usage advice.

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