sophos_mobile_action_send_message

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

With no annotations, the description must cover behavioral traits. It states the message appears as a notification, but lacks details on delivery guarantees, failure handling, rate limits, or what happens if more than 50 IDs are provided. This is insufficient for understanding the tool's behavior fully.

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 two short sentences with no extraneous information. Every word contributes to the purpose and key constraint. Well-structured and efficient.

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 action with 3 parameters and no output schema, the description covers sending a message and its display. However, it lacks information on response behavior, error conditions, and prerequisites (e.g., device enrollment status). Adequate but not thorough.

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 descriptive parameter descriptions. The tool's description adds the 'up to 50' constraint, which is already in the schema. Thus, the description adds minimal value beyond the schema, meeting the baseline.

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 ('Send a push message') and the resource ('mobile devices'), with a specific limit of up to 50 devices. It distinguishes this tool from sibling mobile action tools like 'lock' or 'wipe' by focusing on messaging.

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 when to use (to send a push notification), but does not provide explicit guidance on when not to use it or mention alternatives. The sibling tools are different actions, so context helps, but no direct exclusions or when-to-avoid statements.

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