manage_intune_macos_devices

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

Annotations indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description adds context by listing specific actions like 'wipe' and 'retire' that align with destructive operations, and mentions 'enrollment' and 'device actions' that imply mutations. It doesn't contradict annotations and provides useful behavioral details beyond them, though it lacks rate limit or auth requirement disclosures.

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, efficient sentence that front-loads key functions. It avoids redundancy and wastes no words, though it could be slightly more structured by separating core actions for clarity.

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?

Given the tool's complexity (5 parameters, destructive actions, no output schema), the description is adequate but incomplete. It covers the scope and key actions but lacks details on return values, error handling, or dependencies. With annotations providing safety cues, it meets minimum viability but leaves gaps for an agent to infer behavior.

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 description coverage is 100%, so parameters are well-documented in the schema. The description adds minimal semantics by implying the 'action' parameter includes operations like enrollment and device actions, but doesn't clarify parameter interactions (e.g., deviceId required for wipe but not list). Baseline 3 is appropriate as the schema carries the burden.

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 manages macOS devices in Intune with specific functions (enrollment, compliance policies, device actions, inventory management). It distinguishes from sibling tools like manage_intune_macos_apps or manage_intune_windows_devices by focusing on device management rather than apps or Windows devices. However, it doesn't explicitly contrast with manage_intune_macos_compliance or manage_intune_macos_policies, which handle overlapping aspects.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., device enrollment status), exclusions (e.g., when not to use destructive actions), or refer to sibling tools for related tasks. The agent must infer usage from the action parameter alone.

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