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 states this is a retrieval operation (implying read-only), mentions security context about controllers, and includes pagination parameters (limit/skip) which suggests a list operation. However, it doesn't disclose rate limits, authentication requirements, error conditions, or what format the controllers are returned in.

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 the core purpose, provides background context about AIA CAs, mentions security implications, and then clearly documents parameters. Each sentence earns its place, though the security context sentence could be considered slightly extraneous for pure tool selection.

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 conditions, or authentication requirements. The lack of output schema means the description should ideally explain what 'controllers' data looks like, which it doesn't.

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 provides excellent parameter semantics beyond the schema. While schema description coverage is 0%, the description clearly explains: 'ca_id: The ID of the AIA CA to query', 'limit: Maximum number of controllers to return (default: 100)', and 'skip: Number of controllers to skip for pagination (default: 0)'. This fully compensates for the lack of schema descriptions and adds meaningful context about defaults and purpose.

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 controllers of a specific AIA Certificate Authority.' It specifies the verb ('retrieves'), resource ('controllers'), and target ('AIA Certificate Authority'). However, it doesn't explicitly differentiate from sibling tools like 'get_enterprise_ca_controllers' or 'get_root_ca_controllers' beyond mentioning AIA specifically.

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 some implied usage context by explaining what AIA CAs are and mentioning security implications ('may be able to perform certificate-based attacks'), which suggests when this tool might be relevant. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_enterprise_ca_controllers' or provide clear exclusions.

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