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 the tool retrieves data (implying read-only) and mentions pagination via 'skip' and 'limit', which is useful. However, it lacks details on permissions required, rate limits, error conditions, or the return format (e.g., list structure, fields included). For a tool with no annotations, this leaves significant gaps in understanding its 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 well-structured and front-loaded, with the core purpose in the first sentence and additional context in the second. The parameter explanations are concise and directly relevant. There's minimal waste, though the second 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?

Given 3 parameters with 0% schema coverage and no output schema, the description does a fair job: it covers parameter meanings and implies read-only behavior. However, it lacks details on the return format, error handling, and security implications (e.g., domain context), which are important for a tool in this domain. It's adequate but has clear gaps for effective agent use.

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?

Schema description coverage is 0%, so the description must compensate. It provides clear semantics for all three parameters: 'gpo_id' specifies the target GPO, 'limit' defines the maximum return count with a default, and 'skip' explains pagination with a default. This adds meaningful context beyond the bare schema, though it doesn't detail format constraints (e.g., GPO ID structure).

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 action ('Retrieves') and resource ('computers within a specific GPO'), making the purpose evident. It distinguishes from siblings like 'get_computers' (general) and 'get_ou_computers' (OU-based), but doesn't explicitly contrast them. The second sentence about 'identify potential targets' adds context but isn't essential to the core purpose.

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?

No explicit guidance on when to use this tool versus alternatives is provided. While the description implies it's for GPO-specific computer retrieval, it doesn't mention when to choose it over 'get_computers' or 'get_ou_computers', nor does it discuss prerequisites or exclusions. The agent must infer usage from the purpose alone.

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