sophos_list_mobile_device_violations

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

Without annotations, the description only states it lists violations. It does not disclose if the operation is read-only, has any side effects, or how pagination works (though schema implies it). Adequate but lacks depth.

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 sentence, front-loaded with verb and resource, no wasted words. Meets conciseness expectations.

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 list tool with no output schema, the description could mention output format or typical usage patterns. It is sufficient but does not fully inform about filtering or result expectations.

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%, so baseline is 3. Description adds no additional meaning beyond schema parameter descriptions; it does not clarify required ordering, format, or relationships between parameters.

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 ('List') and resource ('compliance violations for a specific mobile device'). It distinguishes from sibling tools like sophos_list_mobile_devices and sophos_list_mobile_device_scan_results by focusing on violations per device.

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. Does not mention prerequisites, required prior steps, or context like needing to first get the device ID from another tool.

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