sophos_dns_list_policies

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

No annotations provided, so description must carry disclosure burden. It states 'List all' but the input schema includes filters (name, page, etc.), implying behavior is selective, not truly 'all'. Missing details on pagination, sorting, or return structure.

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?

Single clear sentence with no extraneous content. Efficient and direct.

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?

Given 7 parameters (many optional) and no output schema, the description is insufficient. It omits return format, pagination details, and the fact that filters modify the result set. A more complete description would cover these aspects.

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, so baseline is 3. The description adds no additional meaning beyond the schema entries, nor does it clarify usage of optional parameters like page_total or name_contains.

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 tool lists DNS Protection policies for a tenant, specifying the resource (DNS Protection policies) and action (list), which distinguishes it from generic policy list tools like sophos_list_policies.

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 on when to use this tool versus alternatives like sophos_list_policies or other DNS policy tools. The description does not mention filtering capabilities or prerequisite conditions.

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