Retrieve a specific ungrouped firewall policy rule by policy UUID, scope, and rule UUID to inspect its configuration.
Get an ungrouped firewall policy rule.
| Name | Required | Description | Default |
|---|---|---|---|
| scope | Yes | Rule scope: 'global' or 'zone'. | |
| rule_uuid | Yes | ||
| policy_uuid | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description fails to disclose behavioral traits such as read-only nature, return format, or authorization requirements. It only states the basic action without any additional behavioral context.
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?
Description is extremely short but lacks necessary detail. While concise, it is under-specified and does not provide enough information to be useful. Conciseness without completeness is not effective.
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 3 required parameters, no output schema, and no annotations, the description is insufficient. It does not clarify what the tool returns, how to interpret parameters, or any other contextual information needed for correct usage.
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?
Input schema has 3 parameters with only 33% description coverage. The description does not add any meaning beyond the schema; it does not explain the purpose or expected values for policy_uuid or rule_uuid.
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?
Description clearly states the verb 'Get' and the resource 'ungrouped firewall policy rule'. It differentiates from sibling tools like sdcloud_get_firewall_policy_rule_in_group by specifying 'ungrouped'.
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 guidance on when to use this tool vs alternatives. The description does not mention when not to use it or provide any contextual usage hints despite many similar sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.