list_all_clusters

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

With no annotations, the description reveals key behavior: parallel scanning across accounts, default compact summaries, and verbose mode for full configs. However, it omits potential performance or rate-limit implications.

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 brief, front-loads the core purpose, and organizes parameter details in a clear Args section. No redundant text.

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 an output schema exists and the tool is simple, the description covers purpose, behavior, and parameter. It could explicitly differentiate from sibling cluster listing tools, but overall is adequate.

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 single parameter 'verbose' has no schema description (0% coverage), but the description adds full meaning: it controls compact vs full configs, and provides use cases like troubleshooting. This compensates well.

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 'List ALL Ocean clusters across ALL accounts and cloud providers (AWS + Azure)', with specific verb 'list' and resource 'clusters', and the scope distinguishes it from sibling tools like list_clusters which are likely per-account.

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 description implies when to use this tool (for a global view) but does not explicitly compare to siblings like list_clusters or list_clusters_azure, nor mention when not to use it. The 'verbose' parameter guidance is good.

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