list_all_clusters

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

Discloses parallel scanning and return format (compact vs verbose), but no annotations exist. Does not mention rate limits, permission requirements, or potential performance impact.

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?

Five sentences with clear structure: action, behavior, default output, verbose usage, and parameter doc. No wasted words; purpose is front-loaded.

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?

Covers scope, behavior, parameter usage, and return format. With an output schema available, the description is sufficient for an agent to select and invoke correctly.

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' is explained with purpose ('full configurations') and usage context ('analyzing cluster settings, troubleshooting'). Schema only defines boolean type and default; description adds actionable guidance.

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?

Clearly states 'List ALL Ocean clusters across ALL accounts and cloud providers', specifying scope and action. Differentiates from siblings like list_clusters (per-account) and list_clusters_azure (Azure-only).

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?

Describes when to use verbose=true for full configs, and implies cross-account need. However, does not explicitly state when not to use (e.g., preferring filtered tools for specific accounts).

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