ThreatLocker Online Devices

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable behavioral context: listing is paginated, fetchAllPages can auto-fetch up to 10 pages, the action parameter is currently limited to list, and View Computers permission is required. This goes beyond the annotations without contradicting them.

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 well-organized with a short summary, bulleted workflows, permissions, pagination notes, key response fields, and related tools. It is longer than the minimum but every section adds operational value; only minor redundancy exists between 'currently connected' and 'active endpoints'.

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 read-only list tool, the description covers what the tool does, when to use it, permissions, pagination behavior, useful response fields, and related alternatives. The output schema handles return-value specifics, so nothing essential is missing for an agent to invoke the tool correctly.

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 input schema has 100% description coverage, so the baseline is 3. The description adds practical parameter semantics by demonstrating action=list, pageNumber=2, pageSize=100, and fetchAllPages=true in realistic workflows, which helps an agent select parameters meaningfully beyond the raw schema definitions.

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 (ThreatLocker online devices), the operation (query/list), and the outcome (devices currently connected and reporting). It distinguishes itself from related tools by noting computers is for full inventory with details and computer_groups is for membership structure.

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?

Provides explicit common workflows with concrete examples, including checking online count, verifying a specific hostname, monitoring fleet connectivity, and paginating large lists. It also names related tools and their different purposes, giving the agent clear guidance on when to choose this tool versus alternatives.

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