sophos_get_firewall_group

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

The description only states the basic read operation. With no annotations, it should disclose more, such as required permissions, error handling, or response format. It does not describe side effects or behavior beyond the minimal purpose.

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 that immediately conveys the purpose. Every word is necessary and front-loaded.

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 retrieval tool with only two well-documented parameters and no output schema, the description is sufficiently complete. It might be improved by mentioning the expected output (e.g., 'returns group configuration details'), but it's adequate as is.

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 100% with clear parameter descriptions ('Tenant UUID', 'Firewall group UUID'). The description adds no additional meaning beyond the schema, so baseline score of 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?

The description clearly states the verb 'get details' and the resource 'firewall group', and specifies it's for a 'specific' group. This distinguishes it from sibling tools like sophos_list_firewall_groups (lists all) and sophos_get_firewall_group_sync_status (gets sync status only).

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?

No guidance is provided on when to use this tool versus alternatives (e.g., when to use sophos_list_firewall_groups instead). There is no mention of prerequisites, limitations, or context for invocation.

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