sdcloud_list_firewall_policy_rule_groups

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'List rule groups', implying a read operation, but gives no details on pagination, sorting, filtering, or other behaviors. The input schema contains pagination and filtering parameters (from, size, sortby, filters), but the description does not explain their usage or the default behavior.

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 very concise at one sentence, with no wasted words. It is front-loaded with the primary action. However, it could benefit from a bit more structure, such as mentioning required parameters or a brief usage context.

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?

Given the tool has 7 parameters, no output schema, and no annotations, the description is insufficient for an agent to fully understand the tool's behavior. It does not explain what rule groups are, the relationship to policies, or the structure of the response. The agent may need to infer pagination and filtering details from the schema alone, which is suboptimal.

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 86% (high), so the baseline is 3. The description does not add any extra meaning beyond what the schema already provides. It does not explain parameters like policy_uuid, scope, or the pagination options that could help the agent decide how to use them.

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 clearly states the verb (list) and resource (rule groups) and context (within a firewall policy scope). It distinguishes the tool from sibling tools like sdcloud_list_firewall_policy_rules_in_group (which lists rules within a group) and sdcloud_list_firewall_policy_rules (lists all rules). However, it does not explicitly differentiate from other list tools or mention the required parameters.

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 provides no guidance on when to use this tool versus alternatives. No conditions, prerequisites, or exclusions are mentioned. For example, it doesn't suggest using sdcloud_list_firewall_policy_rules_in_group when needing to list rules within a specific group.

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