get_globalprotect_users

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

Annotations already declare the operation read-only and non-destructive, and the description reinforces this with a [READ-ONLY] prefix. It also adds value by disclosing the exact underlying command ('show global-protect-gateway current-user'), which gives the agent concrete knowledge of what will be executed.

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 compact sentences with no filler. The read-only marker and core purpose are front-loaded, and the underlying command is included as useful supporting detail.

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 retrieval tool with one optional parameter, the description is nearly complete: it states what is retrieved, the command executed, and the schema documents the parameter. The lack of an output schema could have been compensated with return-format details, but this is a minor gap.

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%, so the input schema fully explains the 'firewall' parameter. The description itself adds no additional parameter-level meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 ('Retrieves') and resource ('currently connected GlobalProtect VPN users'), and it names the exact command executed. However, it does not explicitly differentiate itself from the sibling tool 'gp_current_users', which appears to serve a similar purpose.

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?

There is no guidance on when to use this tool versus alternatives such as 'gp_current_users' or 'get_globalprotect_config'. The only usage hint is about the optional firewall parameter, which is handled by the schema and does not help with tool selection.

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