list_cni_slots

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 indicates the operation is a list, implying read-only, but provides no detail on pagination, return format, required permissions, or account-level scoping behavior beyond the bare phrase 'for an account'.

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 a single, front-loaded sentence with no filler. Every word contributes to stating the action and scope, which is appropriate for a simple one-parameter list tool.

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 low complexity, one documented parameter, and no output schema, the description is minimally adequate for basic invocation. However, without annotations or an output schema it leaves the agent to infer return structure, pagination, and what a CNI slot actually is, so it is not fully self-sufficient.

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 single required parameter account_id is 100% covered by the schema description, so the schema already explains it. The description's 'for an account' modestly reinforces the meaning but adds lit le beyond the structured field definition.

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 names a specific verb ('List') and resource ('CNI slots') and scopes it to an account, so an agent can tell it performs a read-only listing operation. However it does not distinguish this from sibling tools like list_cni_interconnects or get_cni_settings, so it misses the differentiation tht would merit a 5.

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 given about when to use this tool versus alternatives. The description only states what it does, not when it is the right choice, what prerequisites exist, or how it relates to the CNI-related sibling tools.

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