ThreatLocker System Audit

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds substantial behavioral context: required permissions, pagination behavior with max pages, wildcard support, audit action semantics, and key response fields. This goes well beyond the structured annotation data and helps the agent predict side effects and invocation constraints.

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-structured and front-loaded with a clear purpose, followed by a helpful common-workflow section and concise enum/pagination/permission notes. It is longer than minimal but every section earns its place; only minor redundancy with the schema's parameter descriptions prevents a perfect score.

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 16-parameter tool with two distinct actions, the description is exceptionally complete: it covers both actions, provides concrete usage patterns, explains the key enum values, notes pagination and fetchAllPages, lists required permissions, identifies key response fields, and points to related tools. Since an output schema exists, return-value detail is not required. Nothing critical for correct invocation is missing.

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 the schema already documents every parameter. The description adds extra meaning through examples (e.g., auditAction=Logon with effectiveAction=Denied for failed logins) and clarifies the audit action enum values (Create, Delete, Logon, Modify, Read) and wildcard usage. It doesn't fully compensate for every parameter's nuance, but it meaningfully augments the schema.

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 a specific verb and resource: 'Query ThreatLocker portal audit logs' and immediately clarifies what system audit tracks (administrator actions like logins, policy changes, approvals, configuration modifications). It explicitly differentiates itself from action_log, which tracks endpoint events, so an agent can distinguish this tool from its siblings without ambiguity.

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 gives explicit when-to-use guidance with common workflow examples for both actions (search and health_center), names the related tool action_log as the alternative for endpoint events, and states required permissions (View System Audit, View Health Center). It also explains pagination behavior, making it clear when fetchAllPages should be used.

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