listFirewallAcls

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

With no annotations provided, the description carries the full behavioral burden. It indicates a read-only 'List' operation, but does not disclose pagination, result ordering, default behavior when siteId is omitted, authentication needs, or any output characteristics.

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. The parenthetical adds useful clarification without bloating the definition.

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 simple one-parameter read tool, this is minimally viable, but it leaves gaps: no output schema, no alternative routing guidance, and no explanation of the siteId parameter beyond the phrase 'for a site.' An agent could likely invoke it correctly, but would be guessing about result details and edge cases.

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 input schema provides no description for siteId, and schema description coverage is 0%. The phrase 'for a site' adds some domain meaning, but the description does not clarify siteId's format, whether it is optional, or what happens when it is omitted.

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 states a specific verb ('List'), a clear resource ('firewall ACL rules'), and a scope ('for a site'). The parenthetical clarifies what ACLs are, and the tool is easily distinguished from siblings like createFirewallAcl, deleteFirewallAcl, and getFirewallSetting.

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 usage is implied: use it when you need to list firewall ACL rules for a site. However, it provides no explicit guidance about when to prefer this over related tools like getFirewallSetting or how it differs from firewall settings retrieval.

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