sophos_create_firewall_group

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

Annotations already indicate non-read-only (creation). Description adds the constraint of requiring at least one firewall UUID. No contradiction with annotations, but lacks details on permissions, error handling, or return value.

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, no waste. Purpose and key requirement front-loaded. Efficient use of words.

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?

Short description omits explanation of what a firewall group is, prerequisites (tenant_id), how to get firewall UUIDs, and return behavior. With 5 parameters and no output schema, more context is needed for adequate completeness.

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 100% already documents parameters. Description adds context that assign_firewalls is not just required but must have at least one UUID. Does not explain other parameters like parent_group_id or config_import_source_firewall_id.

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?

Clear verb 'Create' and resource 'firewall group'. Distinguishes from siblings like update/get/list. Also states key constraint about required firewall assignment, adding specificity.

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?

Implied usage for creation (no update/list). Restates requirement from schema but no explicit when/when-not/alternatives. Could mention to use update for existing groups.

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