BloodHound MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden. It discloses that this is a read operation ('retrieves') and provides context about what 'active sessions' means. However, it doesn't mention authentication requirements, rate limits, error conditions, or what the return format looks like. The security context about lateral movement is useful but doesn't fully describe behavioral traits.

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 plus parameter documentation. The first sentence states the purpose, the second clarifies 'active sessions,' and the third provides security context. The Args section is well-structured. Minor typo ('hte' instead of 'the') slightly reduces quality.

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 tool with 3 parameters, no annotations, and no output schema, the description provides adequate coverage of purpose and parameters but lacks details about return format, error handling, and authentication requirements. The security context is helpful but doesn't fully compensate for missing behavioral details.

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 compensates by providing clear parameter documentation in the Args section. It explains group_id as 'The ID of the group to query,' limit as 'Maximum number of sessions to return' with default, and skip as 'Number of sessions to skip for pagination' with default. This adds significant value 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 with specific verb ('retrieves') and resource ('active sessions of the members of a specific group within the domain'). It distinguishes itself from sibling tools like get_user_sessions and get_computer_sessions by specifying group-based session retrieval.

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 implies usage context by mentioning 'potential targets for lateral movement and privilege escalation,' but doesn't explicitly state when to use this tool versus alternatives like get_user_sessions or get_computer_sessions. No explicit exclusions or prerequisites are provided.

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