BloodHound MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves members but doesn't cover critical aspects like whether it's a read-only operation, potential rate limits, authentication requirements, error handling, or the format of returned data. The mention of 'lateral movement and privilege escalation' adds some security context, but overall behavioral traits are inadequately described for a tool with no annotation support.

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 well-structured and appropriately sized. It starts with a clear purpose statement, adds context about memberships, and then lists parameters with explanations. Each sentence serves a purpose, though the security context sentence ('These memberships can be used...') could be considered slightly extraneous if not critical for tool selection. Overall, it's efficient and front-loaded with key information.

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 (3 parameters, no annotations, no output schema), the description is moderately complete. It covers the purpose and parameters well but lacks details on behavioral aspects like return format, pagination behavior, or error conditions. Without an output schema, the description should ideally hint at what's returned (e.g., list of users/groups), but it doesn't, leaving gaps in contextual understanding for the agent.

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 description adds significant value beyond the input schema, which has 0% description coverage. It explicitly documents all three parameters ('group_id', 'limit', 'skip') with clear semantics, including defaults and purposes (e.g., 'skip' for pagination). This compensates fully for the schema's lack of descriptions, making parameter usage understandable without relying on the schema alone.

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 tool's purpose: 'Retrieves the members of a specific group within the domain.' It specifies the verb ('retrieves') and resource ('members of a specific group'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_group_info' or 'get_group_memberships', which might have overlapping or related functionality.

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 no guidance on when to use this tool versus alternatives. It mentions that memberships can be used for 'lateral movement and privilege escalation,' which hints at a security context, but doesn't specify prerequisites, constraints, or when to choose other tools like 'get_group_info' or 'get_users' for related queries. This lack of explicit usage context limits its effectiveness for an AI agent.

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