list_firewalls

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context: it is explicitly '[READ-ONLY]', it 'never API keys' (a privacy guarantee), and it indicates whether the firewall parameter is required in other tools (a response semantic). This goes beyond the annotations and is helpful, though it does not cover edge cases like empty lists or error responses, so it is not a 5.

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 compact and front-loaded with the [READ-ONLY] marker. Every clause adds value: the read-only status, the list purpose, the output contents, the privacy guarantee, and the additional indication about the firewall parameter. No wasted words.

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 zero-parameter tool with no output schema, the description covers the essential return semantics (names, hosts, no API keys, and the firewall-parameter-required indicator). It does not specify the exact response shape (e.g., field names or types), but given the tool's low complexity and the absence of an output schema, it is sufficiently complete for an agent to invoke correctly.

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 has zero properties and the description correctly adds no parameter details. The rule states a baseline of 4 for 0 parameters, and the description does not introduce any conflicting or unnecessary parameter information.

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 and resource: 'Lists all configured firewall targets.' It also clarifies output contents (names/hosts, no API keys) and a secondary purpose (indicating whether the firewall parameter is required). While the sibling set includes panorama_list_firewalls, the description does not explicitly differentiate local versus Panorama, so it is not a 5; however, the name and content make the purpose clear.

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 implies when to use the tool: to enumerate firewall targets and learn whether the firewall parameter is required for other tools. It does not explicitly name alternatives or state when not to use it (e.g., versus panorama_list_firewalls). It provides a clear functional context but no exclusions, so it earns a 3.

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