get_cluster_nodes

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

With no annotations, description must disclose behaviors. It mentions that setting limit=0 returns all results, which adds value. However, it does not discuss pagination, rate limits, or authentication requirements beyond an env var mention. Adequate but not thorough.

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?

Description is well-structured with an Args section. It is front-loaded with the purpose. Could be slightly more concise by removing redundant phrasing, but overall efficient.

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 presence of an output schema (contextual signal), the description does not need to explain return values. It covers all parameters, default behaviors, and a special case (limit=0). Complete for a straightforward list tool.

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 description fully compensates. Each parameter is explained: cluster_id with example format, account_id default to env var, cloud options, and limit with special value behavior. Adds significant meaning beyond the bare 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?

Description clearly states 'List all nodes in an Ocean cluster (AWS or Azure).' This is a specific verb-resource combination that distinguishes it from sibling tools like get_cluster (cluster info) and list_clusters (list 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?

No explicit comparison to siblings or when-to-use scenarios. The description implies usage through its name and purpose, but does not guide the agent on when to use this tool over alternatives like get_cluster or list_vngs.

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