List Firewalls

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

With no annotations provided, the description carries the full burden. It only says 'Get all firewalls,' which indicates a read operation but does not disclose any behavioral traits such as pagination, return format, scoping (e.g., account-wide vs per-VPS), or potential side effects. No additional context is given.

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 one short sentence, 'Get all firewalls,' with no wasted words or irrelevant details. It is front-loaded and easy to parse, making it highly concise and well-structured.

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 tool's simplicity (no params, no output schema), the description could still provide more context, such as the return value (e.g., an array of firewall objects) or scope of the listing. Without this, an agent may not know what to expect from the response or whether 'all' means all in the account or all for a specific VPS. The description is too minimal to be fully complete.

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 tool has zero parameters and the schema is empty (100% coverage by default). The baseline for 0 params is 4, and the description adds nothing about parameters since there are none, which is appropriate. It does not need to explain any input semantics.

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 'Get all firewalls' clearly states the action (get/list) and the resource (firewalls), and it distinguishes from sibling tools like vps_firewall_get (which likely retrieves a single firewall) and vps_firewall_create. It is specific and unambiguous.

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 provided on when to use this tool versus alternatives. For example, it does not mention that vps_firewall_get should be used for a specific firewall, or that this tool lists all firewalls without filtering. The usage is implied by the name but not explicitly stated.

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