sophos_get_firewall_licenses

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's value is limited to adding the tenant/partner context requirement. It does not disclose additional behavioral traits such as pagination behavior or response format, which would be helpful.

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 two concise sentences with no extraneous information. The purpose is front-loaded, and the usage constraint is clearly stated in the second sentence.

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?

The description covers the essential contextual requirement of distinguishing between tenant and partner contexts. However, it does not describe the return structure or license details, which could be inferred from the tool name but lacks explicit documentation.

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 description coverage is 100%, so the baseline is 3. The tool description does not add any extra meaning beyond what the schema already provides for each parameter. It only reiterates the mutually exclusive requirement for tenant_id and partner_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?

The description clearly states the verb 'Get' and the resource 'firewalls and their licenses'. It specifies the scope 'for a Sophos Central tenant or partner', which distinguishes it from other firewall-related sibling tools that do not focus on licenses.

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?

The description provides clear guidance on when to use tenant_id vs partner_id and states that they are mutually exclusive. However, it does not explicitly mention when not to use the tool or suggest alternatives for obtaining the required IDs.

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