bof_adcs

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

No annotations provided, so the description must disclose behavior. It mentions attack types (e.g., PKINIT + UnPAC-the-hash, Shadow Credentials) and gives example commands, but lacks details on side effects, authorization needs, or safety.

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 well-structured with bullet points and examples, efficiently conveying multiple subcommands. It front-loads the purpose and avoids unnecessary verbosity, though it is somewhat lengthy due to the number of examples.

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 complexity of ADCS attacks and the presence of an output schema, the description covers main use cases and examples. However, it lacks context on error handling, prerequisites, and when to use sibling tools, leaving some gaps.

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?

The input schema has generic parameters (agent_id, command, args) with 0% description coverage. The description compensates by showing how to structure the command and args via examples, but does not formally map the subcommand parameters to the schema.

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 the tool's purpose: 'ADCS-BOF: Active Directory Certificate Services attacks.' It lists specific subcommands like certi auth, enum, request, request_on_behalf, shadow with examples, making it distinct from sibling BOF 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 explicit guidance on when to use this tool versus alternatives. While the description shows what each subcommand does, it does not indicate prerequisites, scenarios, or when other tools might be more appropriate.

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