lookup_lolbas

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

No annotations are present, so the description carries the full burden of behavioral disclosure. 'Look up' implies a read operation but doesn't confirm it, and nothing is stated about exact vs. fuzzy matching, case sensitivity, whether the extension is required, or what happens on no match. For a tool with zero annotation coverage, this is a meaningful gap.

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?

A single sentence with zero filler words. The acronym LOLBAS is expanded for clarity, the verb is front-loaded, and every word carries meaning. Nothing could be trimmed without losing information.

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 one-parameter lookup tool, the essential elements (resource, key, purpose) are present. However, with no output schema and no annotations, the agent learns nothing about the result shape, no-match behavior, or safety profile. This is adequate for a simple tool but leaves room for improvement.

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% — the 'binary' parameter already includes a description with concrete examples (certutil.exe, mshta.exe). The tool description reaffirms the parameter's role ('by name') but adds no format constraints, normalization rules, or matching behavior beyond what the schema provides, so the baseline 3 is appropriate.

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 uses a specific verb ('Look up') with a clear resource (LOLBAS binary), the lookup key (by name), and the purpose (abuse techniques). It distinguishes itself from sibling lookup tools for other resource types (lookup_loldriver, lookup_hijacklib, lookup_wadcom). It doesn't explicitly differentiate from list_lolbas, though 'by name' hints at a targeted single-binary lookup rather than enumeration.

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?

No guidance is given on when to use this tool versus alternatives. With a large sibling set including list_lolbas and multiple lookup_* tools differentiated mainly by resource type, the agent must infer selection criteria from the tool name alone. There are no exclusions, prerequisites, or conditions stated.

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