filter_clusters_by_tag

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

Describes default compact summaries vs. verbose full configs, and works for AWS/Azure. No annotations provided, so description carries full burden; it adequately discloses behavior without contradictions.

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?

Well-structured with a brief intro followed by bullet-point argument descriptions. Slightly longer than necessary but earns its length with valuable detail.

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?

Completely covers use case, parameter behavior, output options, and cloud support. Output schema exists, so no need to detail return values.

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 coverage, description explains each parameter (tag_key, tag_value, account_id, cloud, verbose) with examples and usage context, far exceeding schema's minimal info.

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 it filters Ocean clusters by tag key and optionally tag value, specifying the resource and action. Distinguishes from sibling 'filter_vngs_by_tag' by targeting 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?

Provides context for when to use (filtering by tag) and guidance for verbose mode (analyzing cluster settings, troubleshooting). Lacks explicit 'when not to use' or direct alternatives, but sibling names imply differentiation.

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