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 clarifies that the tool retrieves 'active sessions' and implies read-only behavior through the verb 'retrieves', but doesn't explicitly state whether it's safe, requires authentication, has rate limits, or what the output format looks like. The security context about attack paths adds some value, but key operational details are missing.

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 with a clear purpose statement followed by detailed parameter documentation. The first sentence efficiently states the core function, and the 'Args' section is organized. However, the middle sentences about attack paths, while informative, could be more concise or integrated better with usage guidelines.

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 parameters well but lacks output details, error handling, or explicit behavioral traits. The security context is helpful, but for a tool with no structured metadata, more operational guidance would improve completeness.

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 includes an 'Args' section that documents all three parameters with clear semantics: 'computer_id' specifies which computer to query, 'limit' defines the maximum sessions returned with a default, and 'skip' handles pagination with a default. This fully compensates for the 0% schema description coverage, providing essential context beyond the bare schema.

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 active sessions of a specific computer within the domain.' It specifies the verb ('retrieves'), resource ('active sessions'), and scope ('specific computer within the domain'). However, it doesn't explicitly differentiate from sibling tools like 'get_user_sessions' or 'get_group_sessions', which reduces it from a perfect score.

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 potential use cases (e.g., identifying targets for lateral movement), but doesn't specify prerequisites, exclusions, or compare it to related tools like 'get_user_sessions' or 'get_computer_info'. This leaves the agent with insufficient context for optimal tool selection.

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