ad_bloodhound_collect

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

With no annotations provided, the description must fully disclose behavioral traits, but it reveals nothing about what the tool actually does, what artifacts it produces, what permissions are needed, or how it executes. The phrase 'collection' is vague and leaves all behavioral context ambiguous.

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 brief (two words), but this is under-specification rather than effective conciseness. It fails to convey essential information for a complex tool with multiple parameters, making the brevity counterproductive.

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, no output schema, no annotations) and its context among dozens of specialized AD tools, the description is completely inadequate. It provides no operational detail, no return value expectations, and no integration with the surrounding toolset.

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%, and the description does not mention any of the five parameters. It adds no meaning to domain, username, password, dc_ip, or collection_method beyond what the schema already shows (which is just names and types).

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 'BloodHound collection.' is a noun phrase that essentially restates the tool's name (ad_bloodhound_collect). It suggests the tool performs collection related to BloodHound, but lacks a specific verb or resource scope, making it hard to distinguish from sibling AD tools.

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 provided on when to use this tool versus alternatives. Sibling tools like ad_secretsdump, ad_ldap_enum, or ad_kerberoast exist, but the description gives no context for choosing this one, nor any prerequisites or exclusions.

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