sophos_dns_get_policy

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

With no annotations, the description alone indicates a read operation but fails to disclose any behavioral traits like idempotency, permissions needed, or response characteristics. It only states 'Get details' without elaboration.

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 very concise at 7 words, but could include more useful context without sacrificing brevity. It is front-loaded and efficient.

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 get tool with no output schema and full schema coverage, the description is minimal. It lacks information on return format, error conditions, or behavioral details, making it incomplete given the lack of annotations.

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 both parameters documented as UUIDs. The description adds no additional meaning beyond the schema, warranting the baseline score.

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 uses a specific verb 'Get' and resource 'DNS Protection policy', clearly distinguishing it from sibling tools like sophos_dns_list_policies which lists 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 instead of others, such as when to retrieve specific policy details versus listing all policies. No prerequisites or context provided.

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