ThreatLocker Policies

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

The description goes well beyond the annotations: it discloses that update is a full-replace requiring get first, that changes must be deployed, that precedence is first-match-wins, that monitorMode=1 overrides Learning Mode, and that the implementation is payload-verified but not live-tested. These are non-obvious behavioral traits that materially affect safe invocation and are not conveyed by annotations alone.

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 long but topically organized and mostly dense. It earns its length given 46 parameters and 8 actions. However, the full-replace warning is effectively given three times: in the workflow bullet, in the 'IMPORTANT' callout, and again in the Pitfalls section. This redundancy prevents a 5.

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 complex, mutating tool with 46 parameters and many actions, the description covers workflow examples, pitfalls, scoping constraints, permissions, pagination, key response fields, and related tools. An output schema exists, so return-value documentation is not required here, and what is included is sufficient for an agent to select and invoke the tool correctly in most scenarios.

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%, so the baseline is 3, but the description adds substantial meaning: it maps each action to its required parameters, gives concrete example values, explains conditional validity constraints (e.g., allowRequest and killRunningProcesses are Deny-only, ringfencing requires policyActionId=6), and warns about full-replace behavior for nested arrays on update. This is genuinely valuable beyond the property descriptions.

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 opens with 'Manage ThreatLocker policies' and then immediately defines a policy as linking an application (set of file rules) to a computer group with an action. This makes the specific object and domain clear, and the explicit comparison between list_all and list_by_application plus the 'Related tools' section distinguishes it from sibling tools such as network_access_policies and storage_policies.

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 explicitly says when to use list_all vs list_by_application, provides a set of common workflows with required parameters per action, and adds critical routing guidance such as 'After create/update/delete/copy, deploy changes with action=deploy'. Alternatives like applications, computer_groups, and action_log are named and their role in the policy workflow is stated.

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