cloud_list_firewalls

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

No annotations provided. The description does not disclose any behavioral traits such as pagination, rate limits, or that it is a read-only operation. The schema has page/per_page parameters, but the description does not explain their behavior.

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 extremely short (two words), which makes it concise but insufficient. It lacks critical information about parameters and usage, making it under-specified rather than efficiently sparse.

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 does not explain the return value. With 4 parameters and zero parameter descriptions, the description is highly incomplete. It fails to provide necessary context for effective tool use.

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 parameters (page, per_page, name, label_selector) lack any explanation. The description 'List firewalls' adds no meaning to these parameters. The description should compensate but fails to do so.

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 firewalls,' which is a verb+resource. It distinguishes from sibling tools like 'cloud_get_firewall' (single) and 'cloud_create_firewall' (create). However, it does not mention optional filters (name, label_selector) or pagination, which would make it clearer.

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 on when to use this tool versus alternatives like 'cloud_get_firewall' or 'cloud_list_firewalls' with filters. The description lacks information about pagination or filtering options.

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