ad_secretsdump

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

No annotations are provided, so the description carries full burden. It does not disclose behavioral traits like destructive potential, authentication requirements beyond listing parameters, or side effects. It only states the action without context on safety or impact.

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 concise with two sentences and a parameter list. It is front-loaded with the purpose. The parameter list is slightly lengthy but acceptable; could be formatted as a table for clarity.

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 (dumping domain controller secrets), the description covers the basic purpose and parameters. However, it lacks context on prerequisites, expected output format, or warnings (e.g., impact on the DC). Since an output schema exists, return value explanation is not strictly needed, but the description could still be more thorough.

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 adds meaning by explaining each parameter's purpose (e.g., 'target: Specific target (default: DC)', 'hashes: NTLM hash for pass-the-hash (LMHASH:NTHASH)'). This compensates well, though some parameters lack format details.

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 it dumps secrets (NTLM hashes, Kerberos keys) from a domain controller using secretsdump.py, using a specific verb and resource. It distinguishes from sibling tools like ad_kerberoast and ad_asreproast by naming the underlying tool.

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 explicit guidance on when to use this tool versus alternatives, such as when not to use it or prerequisites like network access or required privileges. The description is silent on selection criteria.

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