sophos_mobile_action_locate

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions the reason logging, but lacks details on whether the action is asynchronous, what the response contains, any side effects, or required permissions. The agent cannot infer the post-invocation behavior or output format.

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 a single sentence that conveys essential information without extraneous words. It is well-structured and front-loaded with the primary action.

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 explains the basic action and constraints, but omits important contextual details such as the expected output (no output schema), whether the action is immediate or asynchronous, and how to retrieve the location results. For a trigger tool, these gaps reduce 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?

The input schema covers all three parameters with descriptions, achieving 100% coverage. The description reinforces the reason requirement and the endpoint_ids limit, but adds minimal new information beyond what the schema already provides. 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 action ('Trigger a GPS location request') and the resource ('mobile devices'). The constraint of up to 50 devices and the logging requirement are specified. It distinguishes from sibling tools like sophos_mobile_action_lock or sophos_mobile_action_wipe.

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 indicates the tool is for requesting GPS location, but it does not provide explicit guidance on when not to use it or mention alternatives. With many sibling tools, specifying exclusions or comparisons would improve clarity.

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