ad_ldap_enum

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

The description conveys the core read-only behavior ('Enumerate') and transport/auth choices via use_starttls and tls_verify, but it does not explicitly state that nothing is modified, what permissions are needed beyond credentials, or how failures and empty results behave. With no annotations, the description carries the full behavioral burden, so these gaps matter.

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 leads with the purpose sentence and follows with a tight Args list. It is economical and every line adds information, though the list format leaves no room for contextual notes.

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 tool with seven parameters and an output schema, the parameter coverage is good, but the description omits when-to-use guidance and detailed behavioral context. It is adequate for a straightforward parameterized enum tool, but not a complete guide.

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 Args block compensates by explaining each parameter: domain/username/password, dc_ip as Domain Controller IP or hostname, query with allowed values, and TLS booleans. This is exactly the semantic filling the schema's bare titles omit.

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 opening sentence states a specific action and resource: 'Enumerate Active Directory via LDAP.' The query argument enumerates concrete object types (users, groups, computers, spns, admins, all), and the LDAP qualifier separates it from sibling AD tools like ad_smb_enum, which use a different protocol.

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 about when to choose this over sibling AD tools such as ad_bloodhound_collect, ad_secretsdump, or ad_smb_enum. The description only lists parameters; it does not state prerequisites, exclusions, or a preferred use case.

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