sophos_bulk_isolate_endpoints

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

No annotations are provided, so the description must carry the full burden. It only states the action and HTTP method. Missing behavioral traits such as idempotency, permissions required, rate limits, network impact, or error handling. Minimal disclosure beyond the basic operation.

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 extremely concise: a single sentence that conveys the core purpose. No unnecessary words; every part is essential.

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?

As a bulk mutation tool with no output schema, the description should at least hint at what the response contains (e.g., status, affected endpoints). It does not. However, the tool is relatively straightforward, so the lack of that detail only slightly hinders completeness.

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 description coverage is 100% — each parameter has a description. The tool description does not add any additional meaning beyond what the schema already provides. According to calibration, baseline is 3 when coverage is high and description adds no extra value.

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?

Description clearly states it can 'Isolate or deisolate multiple endpoints at once via POST /endpoints/isolation'. The verb 'isolate/deisolate' and resource 'endpoints' are explicit. This distinguishes it from siblings like sophos_isolate_endpoint and sophos_deisolate_endpoint which operate on single endpoints.

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 explicit guidance on when to use this tool versus single-endpoint alternatives. The 'bulk' aspect implies it's for multiple endpoints, but no 'when to use' or 'when not to use' statements are present. Usage context is only implied.

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