BloodHound MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns a 'Human-readable interpretation' but doesn't specify behavioral traits such as whether it modifies data, requires specific permissions, handles errors, or has performance considerations. For a tool with no annotations, this leaves significant gaps in understanding its operation and constraints.

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 front-loaded with a clear purpose statement, followed by concise parameter and return value explanations. Every sentence earns its place by providing essential information without redundancy, making it efficient and well-structured for quick understanding.

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 complexity (interpreting query results for security analysis), no annotations, no output schema, and 2 parameters, the description is adequate but incomplete. It covers the purpose and parameters but lacks details on output format, error handling, or integration with sibling tools. This is the minimum viable for basic understanding but misses advanced contextual 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 adds meaningful context for both parameters: 'query' is described as 'The original Cypher query that was executed,' and 'result_json' as 'The JSON result from run_cypher_query.' This clarifies their roles and relationships beyond the schema, which has 0% description coverage. Since there are only 2 parameters and the description compensates well, a score of 4 is appropriate.

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: 'Help interpret the results of a Cypher query for offensive security analysis.' It specifies the verb ('interpret'), resource ('results of a Cypher query'), and context ('offensive security analysis'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'run_cypher_query' or 'search_graph', which handle query execution rather than interpretation.

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 by stating it's for 'offensive security analysis' and references 'run_cypher_query' in the parameter description, suggesting it should be used after executing a query. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., direct analysis of raw results) and doesn't mention any exclusions or prerequisites, leaving some ambiguity.

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