BloodHound MCP Server

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

With no annotations provided, the description carries the full burden. It describes what the tool retrieves and the security implications, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or what happens if the computer_id doesn't exist. The description adds value but leaves gaps in operational 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 perfectly structured with a clear purpose statement, explanatory context, and a well-organized Args section. Every sentence earns its place, with no wasted words, and information is front-loaded appropriately.

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?

For a 3-parameter tool with no annotations and no output schema, the description does a reasonable job but has gaps. It explains parameters well and provides security context, but doesn't describe the return format, error handling, or authentication requirements. Given the complexity of security tools, more completeness would be beneficial.

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?

With 0% schema description coverage, the description compensates well by explaining all three parameters in the Args section. It clarifies that computer_id identifies the target computer, limit controls result size with a default, and skip enables pagination with a default. This adds meaningful context beyond the bare 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 verb 'Retrieves' and the resource 'constrained users of a specific computer in the domain', with a specific explanation of what constrained users are. It distinguishes from siblings like get_computer_admin_users by focusing on constrained delegation access rather than admin rights.

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 provides clear context for when to use this tool: to identify potential targets for lateral movement and privilege escalation. It doesn't explicitly state when not to use it or name specific alternatives among siblings, but the context is well-defined.

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