list_firewall_groups

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

No annotations are provided, and the description only says 'List', which implies read-only but does not explicitly state safety, pagination, return format, errors, or any other behavioral traits. The description carries the full burden but fails to disclose meaningful behavior beyond the operation name.

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 concise and front-loaded. The first sentence states the purpose clearly, and the second provides parameter semantics in a compact format. No unnecessary words or repetition.

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?

For a tool with no output schema and no annotations, the description is incomplete. It explains the operation and parameters but lacks any mention of the return value, pagination, error behavior, or prerequisites. It also does not guide the agent on when to use this tool relative to siblings, leaving gaps for correct invocation.

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 description must compensate. It does so by explaining both parameters: host can be a console name, ID, or composite MAC:numericId format; site is a name or ID. This adds useful detail beyond the bare schema definition, though it could clarify their relationship or required format expectations.

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 uses a specific verb 'List' with a clear resource 'firewall groups' and defines what firewall groups are (IP/port sets referenced by firewall rules). It also scopes to a site, distinguishing it from related sibling tools like get_firewall_group or list_firewall_rules.

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?

There is no explicit guidance on when to use this tool versus alternatives. While it mentions firewall groups are referenced by rules, it does not state when to choose this over list_firewall_rules or get_firewall_group. No exclusions or alternative names are given.

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