list_rolls

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

No annotations provided, so description carries full burden. It names the operation (list) which implies read-only, but does not disclose potential side effects, rate limits, or pagination behavior. The output schema covers return values, but behavioral traits are minimally addressed.

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 concise, using a clear first sentence and structured Args list. No extraneous information. Could be slightly improved by front-loading the core action more, 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, the description adequately covers input parameters. However, it lacks mention of pagination, filtering, or result limits. For a listing tool, these are relevant contextual details that are missing.

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 coverage is 0%, so description compensates by adding meaning: cluster_id format example, account_id default environment variable, cloud allowed values. This goes significantly beyond the bare schema types and defaults.

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 deployment rolls for an Ocean cluster (AWS or Azure)', specifying the resource, target, and cloud providers. It distinguishes from sibling tools like 'get_roll' (single) and 'initiate_roll' by using the verb 'list'.

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 by listing required and optional parameters (cluster_id, account_id, cloud) but does not explicitly state when to use this tool over alternatives like 'get_roll' or 'initiate_roll'. Usage context is inferable but not explicit.

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