BloodHound MCP Server

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

With no annotations provided, the description carries full burden. It clarifies this is a read operation ('Retrieves'), mentions pagination behavior through limit/skip parameters, and adds security context about potential abuse. However, it doesn't disclose authentication requirements, rate limits, error conditions, or what the return format looks like (though no output schema exists).

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 appropriately sized with three focused sentences: purpose statement, RDP rights explanation, and security context. The parameter documentation is clearly separated in an Args section. While efficient, the security context sentence could be considered slightly extraneous for pure tool selection, though it provides valuable usage context.

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 reasonably well by explaining parameters and operation purpose. However, it lacks details about return format, error handling, authentication requirements, and explicit differentiation from sibling tools. The security context helps but doesn't fully compensate for missing structural information.

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 fully compensates by explaining all three parameters: 'group_id' identifies the target group, 'limit' controls maximum returns with default value, and 'skip' enables pagination with default value. This adds crucial meaning beyond the bare schema, making parameter purposes and behaviors clear.

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 resource ('RDP rights of a specific group within the domain'), making the purpose explicit. It distinguishes from siblings like 'get_computer_rdp_rights' by specifying group-level rights rather than computer-level, and from 'get_group_info' by focusing specifically on RDP rights rather than general group information.

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 by explaining what RDP rights are and their security implications ('can be abused for lateral movement and privilege escalation'), which suggests this tool is for security auditing. However, it doesn't explicitly state when to use this versus alternatives like 'get_computer_rdp_rights' or 'get_group_info', nor does it provide prerequisites or exclusions.

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