bof_ad

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions 'no elevated privileges needed' for one subcommand but fails to describe side effects, permissions required, or output format for most commands.

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 a dense block of text with multiple subcommands and examples. It is not concise; it could be structured into sections or bullet points. Every sentence contains useful information, but the lack of formatting reduces 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 (multiple subcommands) and the existence of an output schema, the description is incomplete. It does not mention return values, error states, or how to use the output. The agent must infer parameter usage from examples, which is insufficient.

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 0% coverage, so the description must compensate. It indirectly defines the 'command' parameter by listing subcommand names and shows usage via examples, but it does not explicitly describe parameter types, allowed values, or how 'args' relates to the syntax.

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 'AD-BOF: Active Directory exploitation commands' and lists numerous subcommands, making the tool's purpose evident. However, it does not differentiate itself from sibling tools like bof_ldap or bof_adcs, which also target AD operations.

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. The description lacks any selection criteria or context that would help an agent decide between bof_ad and other bof_* tools.

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