sophos_isolate_endpoint

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

With no annotations, the description carries the burden. It discloses the key behavioral trait that the endpoint only communicates with Sophos Central. It does not mention reversibility, prerequisites, or permission requirements, but the core behavior is well described.

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 with two sentences. The first sentence states the action, the second adds effect and use case. No unnecessary words, perfectly front-loaded.

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 there is no output schema, the description does not explain return values. It also omits side effects or prerequisites. However, for an isolation tool, the core purpose and behavior are covered. The sibling sophos_get_isolation_status exists to check status, which complements this tool.

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%, and the description does not add extra meaning beyond the schema. The parameters (tenant_id, endpoint_id, comment) are self-explanatory from their names and schema descriptions. Baseline 3 applies as no additional value is provided.

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 action ('Isolate an endpoint from the network'), explains the effect ('only able to communicate with Sophos Central'), and specifies the use case ('incident response to contain a compromised machine'). This distinguishes it from siblings like sophos_deisolate_endpoint and sophos_bulk_isolate_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?

The description tells when to use the tool ('for incident response to contain a compromised machine'). It does not explicitly state when not to use it or list alternatives, but the context is clear. The sibling sophos_deisolate_endpoint implies reversal, which is an indirect guideline.

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