sophos_dns_list_custom_domains

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description's 'List' verb aligns with a read-only operation, but it adds no additional behavioral context beyond what annotations provide, such as rate limits or scope of results.

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, front-loaded sentence of 10 words, with no wasted words. It efficiently conveys the tool's purpose and resource.

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?

While the annotations cover the read-only nature, the description lacks information about return values (no output schema), pagination behavior, or how to interpret results. Given the tool has 8 parameters including pagination, more context would help the agent, but the description is minimally acceptable.

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?

The input schema has 100% description coverage for all 8 parameters. The description does not add any extra meaning about the parameters (e.g., format, constraints, or required ones) beyond the schema, so the 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 'List' and the resource 'custom domain lists (allowed/blocked)' for DNS Protection, making the primary purpose evident. It implicitly distinguishes from sibling tools like sophos_dns_get_custom_domain by using 'list' (plural) versus 'get', but does not explicitly differentiate.

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 no guidance on when to use this tool versus alternatives such as sophos_dns_get_custom_domain, sophos_dns_create_custom_domain, or sophos_dns_update_custom_domain. There is no mention of prerequisites, filtering, or pagination limits.

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