bof_kerbeus

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

No annotations are provided, so the description carries full burden. It discloses some behaviors (e.g., 'without elevation via GSS-API' for tgtdeleg) but does not mention required permissions, destructive potential, rate limits, or side effects like ticket purging or password changes.

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 lengthy due to many subcommands but is well-organized with each line representing a command. It front-loads the overall purpose, but contains more detail than strictly necessary, reducing conciseness.

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 Kerberos operations and the 3-parameter schema, the description covers the subcommands thoroughly. However, it lacks details on return values (though output schema exists), error conditions, and agent_id semantics, leaving 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?

Schema coverage is 0%, but the description adds significant value for 'command' and 'args' by listing all subcommands with required arguments and examples. However, 'agent_id' is not explained beyond its schema definition.

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 begins with 'Kerbeus-BOF: Kerberos ticket operations and attacks', clearly stating the tool's purpose. It lists many specific subcommands, making it distinct from sibling BOF tools like bof_ad or bof_creds.

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?

The description implies usage for Kerberos operations but does not explicitly state when to use this tool over alternatives. No 'when not to use' or comparisons to siblings are provided; context is clear but not directive.

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