Update firewall policy (safe)

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

Annotations already indicate non-readonly, non-destructive, idempotent, and open-world. Description adds valuable behavioral context: reads current policy first and defaults to dry_run=true. No contradiction with annotations.

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?

One short sentence efficiently conveys two key behaviors. Front-loaded with verb and safety qualifier. Could be slightly more structured but is already concise.

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?

Tool has 27 parameters and no output schema; description is very brief. Does not explain return format, behavior after dry_run, or how to apply changes. For a complex tool, this is incomplete.

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 78% (high), so baseline is 3. Description adds no additional parameter meaning beyond what the schema already provides. Does not explain any of the 27 parameters.

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 'update a firewall policy', distinguishing it from create tools. Verb 'update' and resource 'firewall policy' are specific. Sibling tools include create_policy, so purpose is unambiguous.

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?

Implies usage for safe updates via 'reads current policy first' and 'defaults to dry_run=true', but does not explicitly state when to use this vs. create_policy or other update tools. Lacks direct when-not guidance.

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