Spotinst MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a listing operation but doesn't describe pagination behavior, rate limits, authentication requirements, error conditions, or what happens when no clusters exist. The description provides minimal behavioral context beyond the basic operation.

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 appropriately sized with two sentences: one stating the purpose and another explaining the parameter. The information is front-loaded with the core purpose first. No wasted words, though the structure could be slightly improved by separating the parameter explanation more clearly.

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 tool has an output schema (which handles return values) and only one parameter with good description coverage, the description is adequate but incomplete. For a listing tool with no annotations, it should ideally mention pagination, result format hints, or authentication context to be fully complete.

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 description provides meaningful context for the single parameter 'account_id', explaining it's optional and defaults to an environment variable. With 0% schema description coverage, this compensates well by adding practical usage information that the schema alone doesn't provide.

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 the verb 'List' and specifies the resource as 'AWS Ocean Kubernetes clusters in a Spotinst account'. It distinguishes from general listing tools but doesn't explicitly differentiate from similar siblings like 'list_all_clusters' or 'list_clusters_azure'.

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 is provided on when to use this tool versus alternatives like 'list_all_clusters' or 'list_clusters_azure'. The description mentions the resource scope but doesn't explain the selection criteria or context for choosing this specific listing tool.

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