list_firewall_rules

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

With no annotations, the description relies on 'List' to signal a read-only action and adds scoping detail for host and site identifiers. It does not disclose pagination, output shape, permissions, or rate-limit behavior, so behavioral transparency is only partial.

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 compact: one sentence states purpose and distinction, and one sentence covers both parameter formats. Every phrase earns its place, and key information is front-loaded.

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 two-parameter read operation with no annotations or output schema, the description covers the essential invocation details well. It leaves minor gaps such as return format/pagination and does not explicitly compare to list_firewall_policies or list_firewall_groups, but these are not critical for making a correct call.

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 schema provides no property descriptions (0% coverage), but this description compensates by defining both required parameters: host accepts console name, ID, or composite ID in MAC:numericId format, and site accepts site name or ID. This gives practical, format-level meaning beyond the bare string schema.

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?

Description opens with the verb 'List' and a specific resource type, 'classic L3/L4 firewall rules', scoped to a site. The parenthetical 'distinct from Integration API policies' further differentiates it from potential sibling confusions, making the purpose clear 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?

The description gives clear context for the operation and explicitly excludes one alternative ('Integration API policies'). It does not mention other relevant alternatives such as get_firewall_rule or list_firewall_policies, but the intended use case is clear enough for a list operation.

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