panorama_get_pre_rules

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description carries less burden. The added config path and parenthetical clarifies the read target and pre-rule semantics, providing useful behavioral context beyond the annotation.

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?

Two tightly written sentences with the read-only marker front-loaded. The config path is included without redundancy, and there is no filler text.

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 read-only tool with full parameter schema coverage and safety annotations, the description is nearly complete. It could mention the returned output shape, but nothing required to invoke the tool correctly is omitted.

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 coverage is 100%, so the schema fully documents device_group and firewall. The description adds little beyond the schema, which is acceptable; only marginal clarification about device group context is provided.

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?

Describes a specific operation: retrieving pre-rules from a device group and clarifies what pre-rules are: rules pushed before local firewall rules. The config path reinforces exactly what resource is addressed, making it easy to distinguish from panorama_get_post_rules and get_security_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?

The description gives clear context: pre-rules are device-group-level rules pushed before local firewall rules. It does not explicitly state when to use this over alternatives such as panorama_get_post_rules.

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