panorama_get_shared_address_groups

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the concrete config source path '/config/shared/address-group', giving useful behavioral context beyond the annotations. It does not discuss authentication or error behavior, but the simple read-only nature and annotation coverage make that less critical.

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 two short sentences with no filler. It front-loads the read-only action and scope, then adds the precise config path. Every sentence contributes useful information.

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 one optional parameter and no output schema, the description plus schema and annotations are complete. An agent knows what the tool retrieves, where it reads from, and when the firewall parameter matters. Nothing essential is missing 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 100%, and the single optional 'firewall' parameter is already well documented in the schema, including when it is required. The tool description itself adds no parameter-level detail, so it does not go beyond the baseline, which is acceptable given the schema coverage.

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: 'Retrieves shared address groups defined at Panorama level.' This clearly distinguishes it from local address group tools and from other shared-object tools such as panorama_get_shared_address_objects. Including the config path '/config/shared/address-group' reinforces the exact scope.

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: this tool is for Panorama-level shared address groups, not device-level or device-group-level groups. It does not explicitly name alternatives or state when not to use it, but the Panorama-level scoping is sufficiently explicit for an agent to route correctly.

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