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 of behavioral disclosure. It correctly indicates a read operation ('retrieves'), but lacks details about permissions required, rate limits, pagination behavior beyond basic skip/limit parameters, error conditions, or what the return format looks like. The security context hint ('identify potential targets') adds some value but doesn't cover 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 appropriately sized with three sentences: purpose statement, use case context, and parameter documentation. The parameter section is clearly formatted. While efficient, the use case sentence could be considered slightly extraneous for pure tool selection, though it provides valuable 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 read tool with no annotations and no output schema, the description is minimally adequate. It covers the basic purpose and parameters but lacks information about return format, error handling, authentication requirements, and performance characteristics. The security context helps but doesn't compensate for these operational 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?

With 0% schema description coverage, the description fully compensates by documenting all three parameters with clear semantics: gpo_id identifies the target, limit controls result size with default, and skip enables pagination. The description provides meaning beyond what the bare schema offers, though it doesn't specify format requirements for gpo_id or constraints on limit/skip values.

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 ('users within a specific GPO'), making the purpose unambiguous. It distinguishes from siblings like 'get_gpo_computers' or 'get_gpo_info' by focusing specifically on users. However, it doesn't explicitly differentiate from other user-related tools in the sibling list.

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. While it mentions a use case ('identify potential targets for lateral movement and privilege escalation'), this is contextual rather than operational guidance. There's no mention of prerequisites, when to choose this over other user retrieval tools, or any exclusions.

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