create_dfw_rule

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

The description states that calling again with the same rule_id replaces the rule, which is idempotent behavior, but the annotation sets idempotentHint=false. This contradiction violates the scoring rule, resulting in a score of 1 despite otherwise detailed disclosure of PUT semantics, enforcement, auditing, and error returns.

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 well-structured: a concise one-line summary, followed by behavioral details, usage guidance, and a clearly formatted parameter list. Every sentence adds essential information without redundancy. Despite length, it is appropriately detailed for the tool's complexity.

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?

Covers purpose, behavior (PUT, immediate enforcement, auditing), usage prerequisites, parameter details, return values (dict with fields), error format, and even risk level. For a complex write tool with 15 parameters and no output schema, this description provides complete context for an AI agent to use it correctly.

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?

The schema has 0% description coverage, but the description's 'Args:' section thoroughly explains each of the 15 parameters, including format, defaults, valid values (e.g., action: ALLOW, DROP, REJECT, JUMP_TO_APPLICATION), examples (e.g., sources paths), and context (e.g., 'as returned by list_dfw_policies'). This adds significant meaning beyond the schema.

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 explicitly states 'Create a firewall rule under an existing DFW security policy,' identifying the specific verb and resource. It distinguishes from siblings by mentioning 'prefer update_dfw_rule' and 'delete_dfw_rule' for modifications and deletions. The PUT behavior and idempotent overwrite are also clarified.

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?

Provides explicit guidance: 'Pick the policy_id with list_dfw_policies first; to change selected fields of an existing rule prefer update_dfw_rule, and to remove one use delete_dfw_rule.' It also explains when to use disabled=True and notes pre-checks and auditing, giving clear context for using this tool versus alternatives.

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