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 discloses the critical security implication ('can issue arbitrary certificates and potentially compromise the domain'), which is valuable behavioral context. However, it doesn't mention authentication requirements, rate limits, error conditions, or what format the returned controllers are in (e.g., user objects, group objects, or identifiers).

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 and front-loaded: the first sentence states the core purpose, the second explains the security significance, the third provides usage context, followed by a clean parameter section. Every sentence earns its place with zero wasted words.

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 well on purpose and parameters but has gaps. It doesn't describe the return format (what a 'controller' object contains), error conditions, or authentication requirements. The security context is helpful, but operational details are missing for complete agent understanding.

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 providing clear semantic explanations for all three parameters: ca_id ('The ID of the Enterprise CA to query'), limit ('Maximum number of controllers to return'), and skip ('Number of controllers to skip for pagination'). It even includes default values not present in the schema annotations.

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 specific action ('Retrieves') and resource ('controllers of a specific Enterprise Certificate Authority'), distinguishing it from sibling tools like get_enterprise_ca_info (which retrieves CA info rather than controllers) and get_root_ca_controllers (which targets root CAs instead of enterprise CAs). The mention of ESC3/ESC6 attack paths further clarifies the security context.

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 about when to use this tool (for identifying ESC3/ESC6 attack paths by finding controllers who can issue arbitrary certificates), but doesn't explicitly mention when NOT to use it or name specific alternatives. It implies usage for security auditing rather than general administration.

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