create_firewall

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

No annotations, so description must provide behavioral context. States scope requirement and that it's a 'plain write — not gated,' indicating no extra guardrails. Does not mention idempotency, error behavior, or whether it returns the created resource.

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?

Two sentences plus a short parameter note. Front-loaded with action and prerequisites. No redundant information. Every sentence adds value.

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?

For a simple one-parameter creation tool with no output schema, the description covers what, prerequisites, and subsequent steps. Could mention return value or synchronous nature, but overall adequate.

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 covers 100% of parameters with descriptions. Description repeats schema info ('name is the display name (1-63 chars)') without adding new semantic meaning. Baseline 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?

Clearly states action: 'Create a new cloud firewall (security group).' Distinguishes from siblings by mentioning 'Add rules with add_firewall_rule, then attach it to a VM with attach_firewall.' Highlights requirement 'Requires scope services:write.'

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?

Explicitly states required scope and that it's a plain write (not gated). Implicitly guides usage order: create firewall, add rules, attach. Lacks explicit when-not-to-use or alternative tools.

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