manage_intune_scripts

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

With no annotations, the description carries the full transparency burden. It discloses action-specific requirements, notably confirm=True for delete, and the valid script_type values. It could add warnings about side effects of update/assign, but it covers the most critical destructive behavior.

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 uses a compact action table format, with each line earning its place by showing which parameters apply. It is longer than two sentences but structured efficiently; no filler exists.

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 tool with seven actions and six parameters, the description defines the operation matrix almost fully. The `top` parameter is left to the schema, and an output schema exists to cover result format. Minor gaps around pagination and edge cases prevent a perfect score.

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?

The schema has 0% description coverage, but the description fully compensates by mapping each action to its required parameters and defining the script_type enum (powershell, remediation, macos). This goes far beyond the bare schema, providing essential semantic meaning.

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 identifies the resource (Intune scripts, remediations, macOS shell scripts) and the verb 'Manage', then enumerates seven concrete actions. This makes it distinctly different from sibling tools like manage_intune_apps or manage_intune_devices.

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 first line states the scope, and the action list implies when to use it (any script management need). It does not explicitly say when not to use it or name alternatives, but the context is unambiguous enough for an agent to select it appropriately.

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