sophos_get_mobile_device

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

No annotations are provided, so the description carries the full burden. It indicates a read operation but does not explicitly state it is read-only, nor does it mention any side effects, authentication needs, or rate limits. The description is sufficient for a typical GET endpoint but could be more explicit about safety.

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 succinctly conveys the essential purpose and key return fields. No redundant or extraneous 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?

There is no output schema, so the description partially compensates by listing included fields (compliance, apps, platform, policies). It covers key aspects but omits the full scope of return data and does not detail required parameters (e.g., tenant_id is required but not mentioned). Still, it provides sufficient context for most use cases.

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%, so parameters are already documented. The description adds context by mentioning the device ID (mapping to device_id) but does not clarify tenant_id or the optional fields parameter. The description provides some additional meaning but does not go beyond the schema significantly.

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 retrieves full details for a specific mobile device by ID, listing included attributes (compliance status, installed apps, platform, assigned policies). It distinguishes from sibling list tools (e.g., sophos_list_mobile_devices) which return summaries, and from other get tools targeting different resources.

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 implies usage when you need detailed information for one device, but does not explicitly state when to use this tool versus alternatives like sophos_get_mobile_device_group or sophos_list_mobile_devices. No exclusionary guidance is provided.

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