sdcloud_bulk_move_firewall_policy_rules

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

With no annotations, the description carries full burden. It only states the action and body fields, omitting behavioral traits like atomicity, partial failure handling, permissions, rate limits, or side effects. Significant gap.

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 a single concise sentence followed by body field names. It front-loads the action. While efficient, it sacrifices some informative content for brevity.

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?

The description lacks context for a complex bulk operation. No output schema, no mention of return values, error handling, prerequisites (e.g., policy existence), or behavior on failure. The nested body object is underspecified.

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 67% (two of three params described). The description adds meaning by naming expected body fields (rule_uuids, target_rule_group_id, position, target_scope) beyond the schema's generic 'JSON request body'. However, policy_uuid is not described, and field semantics within body are not explained.

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 action (Bulk-move firewall policy rules) and the target (target rule group/scope/position). It distinguishes from siblings like sdcloud_move_firewall_policy_rule_in_group by emphasizing bulk operation.

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 implies usage for moving multiple rules at once via the 'Bulk' prefix and body fields, but lacks explicit guidance on when to use versus alternatives or prerequisites (e.g., policy must exist). No when-not-to-use information.

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