get_cluster_nodes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains that limit=0 returns all results, specifies defaults (cloud: aws), and gives an example for cluster_id. Although it does not explicitly state that the operation is read-only, the verb 'List' strongly implies no side effects.

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 very concise: a one-line purpose followed by a bulleted list of parameters. Each sentence is informative without redundancy. It is well-front-loaded with the main action.

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 that an output schema exists (and likely describes the return format), the description covers the operation's purpose, all parameters with examples and defaults, and the limit behavior. It is sufficient for an AI agent to understand and use the tool correctly without additional context.

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?

Schema description coverage is 0%, so the description must compensate fully. It provides meaningful details for all 4 parameters: explains cluster_id with example, account_id with env var default, cloud with allowed values, and limit with special value 0 behavior. This adds significant value beyond the raw schema.

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 nodes in an Ocean cluster (AWS or Azure)', which is a specific verb (List) and resource (nodes in a cluster). This distinguishes it from sibling tools like list_clusters (which lists clusters) or get_cluster (which gets cluster details).

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 usage context (when you need nodes for a specific cluster) but does not explicitly state when to use this tool versus alternatives like get_cluster or list_clusters. It provides parameter guidance but no explicit when-not-to or alternative recommendations.

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