sophos_create_mobile_device_property

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

Annotations already declare readOnlyHint=false (write) and destructiveHint=false (non-destructive). The description adds the key pattern constraint, but does not disclose what happens if the key already exists (overwrite vs. error), response behavior, or any side effects. This is adequate but minimal.

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: two sentences. The first states the primary purpose, and the second adds a critical constraint. No filler words or redundant 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 4-parameter tool with no output schema, the description covers the essential operation and key constraint. However, it lacks detail on what happens if the key already exists, which is a behavioral gap. Nevertheless, it is mostly complete given the tool's simplicity.

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% with all parameters described. The tool description reinforces the key pattern constraint already present in the schema. It adds no further parameter semantics beyond what the schema provides, so a baseline of 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 ('Add a custom property'), the target resource ('mobile device'), and the nature of what's being added ('key/value pair'). It also provides a specific constraint on the key format, distinguishing it from sibling tools like sophos_create_mobile_device (which creates a device) or sophos_update_mobile_device (which updates device fields).

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 needing to add a custom property to an existing mobile device. However, it does not explicitly state when to use this tool versus alternatives (e.g., sophos_create_mobile_device, sophos_update_mobile_device), nor does it provide prerequisites (e.g., device must exist) or when not to use it.

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