ad_ldap_enum

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

No annotations are provided, so the description must disclose behavior. It only lists parameters and a one-line purpose. It does not describe whether the tool is read-only, what side effects occur, how it handles failures, or what output format to expect beyond the existence of an output schema.

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 extremely concise: one line of purpose followed by a cleanly structured argument list. No redundant information. Every sentence earns its place.

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?

Given the tool's complexity (5 parameters, 3 required) and the presence of an output schema, the description is minimally adequate. It explains parameters but does not describe the enumeration behavior, error handling, or any prerequisites like network access. Additional context would improve usability.

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%, but the description explains each parameter in a 'Args:' block, e.g., 'domain: AD domain', 'query: Query type (users, groups, computers, spns, admins, all)'. This adds meaningful context beyond the schema's titles and defaults.

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 'Enumerate Active Directory via LDAP', specifying the verb and resource. The argument list includes query types (users, groups, computers, spns, admins, all), distinguishing it from sibling AD tools like ad_kerberoast or ad_bloodhound_collect.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, contexts, or when to avoid using it. Sibling tools exist for other AD operations, but no selection criteria are given.

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