sophos_scan_endpoint

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

The description discloses that the scan runs asynchronously and this call initiates it, which is a key behavioral trait. No annotations are provided, so there is no contradiction. However, it does not mention potential side effects, required permissions, or how to monitor the scan progress.

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 sentences total, each sentence serves a distinct purpose: the first states the action, the second clarifies asynchronicity. No unnecessary words.

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?

The description does not explain return values or how to retrieve scan results. Without an output schema, the agent is left guessing about the response format. Completeness is insufficient for a tool that triggers an async operation.

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?

Both parameters (tenant_id, endpoint_id) have descriptions in the input schema. The tool description does not add additional detail beyond what the schema provides. With 100% schema coverage, baseline 3 is appropriate.

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 tool triggers an on-demand scan on an endpoint. The verb 'trigger' and resource 'scan on an endpoint' are specific. Among siblings, there is no other 'scan_endpoint' tool, and the name itself differentiates it from mobile device scan 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?

No guidance on when to use this tool versus alternatives like isolation or other endpoint actions. The description mentions asynchronicity but does not provide context about prerequisites or what other tools might be used alongside it.

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