sophos_dns_update_policy

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

With no annotations, the description carries the full burden. It adds specific behavior for array fields (full replacement, clear, add/remove) but does not discuss idempotency, permissions, error cases, or behavior for non-array fields.

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 concise sentences. The first states purpose, the second provides critical parameter handling instruction. No redundant information.

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 13 parameters and no output schema, the description provides purpose and array handling but lacks context on update semantics (merge vs. replace), error handling, and prerequisites. Adequate but not comprehensive.

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 description adds meaningful guidance beyond the schema by explaining how to handle array fields (full replacement, null, add/remove). Schema coverage is 100%, so the baseline is 3, but the extra parameter handling information justifies a 4.

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 name and description clearly state that the tool updates a DNS Protection policy. The description distinguishes it from sibling tools like sophos_dns_create_policy, sophos_dns_delete_policy, and generic update_policy tools.

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 implies usage for updating existing DNS policies but does not explicitly state when to use this tool versus alternatives. No exclusion criteria or conditions are provided.

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