sdcloud_list_firewall_policies

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

No annotations provided, so the description carries the full burden for behavioral disclosure. It only states the basic operation with optional parameters, but does not mention return format, ordering limitations, side effects, or other behavioral context. The description is too minimal.

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 (one sentence) and front-loaded. It efficiently communicates the core action. While it could be slightly expanded for clarity, it has 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?

Given the number of sibling tools and no output schema, the description lacks completeness. It does not explain what is returned or how this tool fits into the broader context of firewall policy management. The minimal description is insufficient for an agent to fully understand scope.

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 already documents each parameter. The description adds a high-level summary ('pagination, filtering, sorting') but does not provide any new meaning beyond what the schema offers. Baseline score of 3 is appropriate.

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 'List firewall policies' with specific verb and resource, and mentions optional pagination, filtering, and sorting. This distinguishes it from sibling tools like sdcloud_list_firewall_policy_assignments and sdcloud_list_firewall_policy_hierarchy.

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?

No explicit guidance on when to use this tool versus alternatives. For example, it does not mention that this lists policies themselves, while other list tools cover assignments or hierarchy. Lacks when-not and alternative references.

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