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 information' and 'provides a general overview,' which implies a read-only operation, but doesn't clarify permissions needed, rate limits, pagination, error conditions, or what 'other attributes' might include. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 and front-loaded: the first sentence states the core purpose, followed by additional details and the parameter explanation. The 'Args:' section is well-structured. However, the reconnaissance/targeting sentence is somewhat vague and could be more precise.

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 tool's low complexity (1 parameter, no nested objects) but lack of annotations and output schema, the description is minimally adequate. It covers the purpose and parameter semantics but lacks behavioral details like error handling or output format. For a read-only query tool, this is borderline but meets basic needs.

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 the single parameter 'group_id' with a brief explanation: 'The ID of the group to query.' With schema description coverage at 0% (the schema has no descriptions), this adds meaningful context beyond the bare schema. However, it doesn't specify the format or source of the group_id, leaving some ambiguity.

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 information about a specific group in a specific domain' and 'provides a general overview of a group's information including their name, domain, and other attributes.' This specifies the verb (retrieves), resource (group information), and scope (specific group in specific domain). However, it doesn't explicitly differentiate from sibling tools like 'get_groups' (which likely lists multiple groups) or 'get_group_members' (which focuses on members).

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 minimal usage guidance. It mentions 'It can be used to conduct reconnaissance and start formulating and targeting groups within the domain,' which implies a security/analysis context but doesn't specify when to use this tool versus alternatives like 'get_groups' or 'get_group_members.' No explicit when/when-not scenarios 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.