sophos_mobile_action_locate

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

Annotations already indicate write behavior (readOnlyHint: false). Description adds that the action triggers a GPS request, is limited to 50 devices, and logs the reason. However, it omits whether the request is asynchronous and how to retrieve results, leaving behavioral gaps beyond what annotations convey.

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 efficient sentences: first identifies action and scope, second a critical constraint. No wasted words, front-loaded with essential information.

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 simple, single-action tool, the description covers key aspects. However, it lacks follow-up context (e.g., checking request status via get_mobile_action) and does not connect to sibling tools for completing the workflow. With no output schema, more context on expected results would improve 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 covers 100% of parameters with descriptions. Description reinforces the reason's logging purpose and the count limit, adding minor value. For a 3-param tool with full schema coverage, the description does not significantly enhance parameter understanding beyond the schema itself.

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 the action ('trigger a GPS location request') on a specific resource ('mobile devices') with a capacity limit ('up to 50'). It distinguishes from sibling mobile actions like sync or get_logs by specifying the location intent.

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. While it notes a reason is required and logged in the privacy log, it does not mention prerequisites, post-action steps, or scenarios where a different action (e.g., sync) would be more appropriate.

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