find_all_enabled_kerberoastable_users

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

No annotations are provided, so the description carries the full burden. It mentions 'Find all enabled kerberoastable user(s)', implying a read-only search operation, but doesn't disclose behavioral traits like required permissions, rate limits, output format, or whether it's destructive. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 single, efficient sentence with no wasted words, making it appropriately sized and front-loaded. However, it's overly terse, bordering on under-specification, which slightly reduces its effectiveness despite the 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 tool's complexity (involving security-specific terms like 'kerberoastable'), lack of annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't provide enough context for an agent to understand the tool's full scope, behavior, or how to interpret results, making it inadequate for effective use.

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 1 parameter with 0% description coverage, and the tool description doesn't mention any parameters. The description fails to add meaning beyond the schema, such as explaining what the 'domain' parameter expects (e.g., a domain name format) or its role in the search. With low schema coverage, the description doesn't compensate, leaving the parameter undocumented.

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 'Find all enabled kerberoastable user(s)' states a verb ('Find') and resource ('enabled kerberoastable user(s)'), giving a vague purpose. It doesn't specify what 'kerberoastable' means in this context or how it differs from similar tools like 'find_all_enabled_as_rep_roastable_users', leaving the agent to infer technical details.

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. With many sibling tools focused on user enumeration and security vulnerabilities (e.g., 'find_all_enabled_as_rep_roastable_users', 'list_enabled_users'), the description lacks context about specific use cases, prerequisites, or exclusions, offering minimal help for selection.

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