manage_compliance_policies

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

With no annotations, the description must disclose behavioral traits. It mentions the delete confirm flag and provides action semantics, but it lacks information about side effects, permissions, reversibility, or error behavior. The transparency is 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 concise and well-structured: a one-sentence purpose followed by a clear bullet-point list of actions with parameters. Every line carries information and there is no fluff.

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?

The action list covers the main operations, but the tool is complex (8 actions) and lacks operational context like prerequisites, pagination, or permission requirements. Output schema exists, so return values are covered, but the description could still provide more guidance on action-specific edge 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 description coverage is 0%, so the description must add parameter meaning. It does map each action to its parameters (e.g., get uses policy_id, delete uses policy_id + confirm, assign uses policy_id + body with assignments), but it stops short of describing the body structure for create/update or the semantics of `top`.

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 'Manage Intune device compliance policies — CRUD, assignment and status' followed by a detailed action list. This uses a specific verb and resource, making the tool's purpose unambiguous and distinguishing it from siblings like manage_configuration_profiles.

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 action list implies when to use this tool (e.g., when you need to manage compliance policies), but there are no explicit exclusions or alternatives mentioned. Sibling tools exist but the description does not guide the agent on when to choose this over others.

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