Set a parent entity to organize knowledge graph entries hierarchically, or use null to remove the parent.
Set the parent of an entity for hierarchical organization
| Name | Required | Description | Default |
|---|---|---|---|
| entityName | Yes | ||
| parentName | Yes | Parent entity name or null to remove parent |
Changes observed during successful MCP inspections.
v11.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It states the tool sets or removes a parent, implying mutation, but doesn't disclose behavioral traits such as permissions needed, whether changes are reversible, error handling, or impact on related entities. This is inadequate for a mutation tool with zero annotation coverage.
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 a single, efficient sentence that is front-loaded and wastes no words. Every part contributes directly to understanding the tool's purpose.
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 (mutation with hierarchical effects), lack of annotations, no output schema, and incomplete parameter documentation, the description is insufficient. It should cover more behavioral aspects and usage context to be complete for safe agent invocation.
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 50% (only 'parentName' has a description). The description adds meaning by clarifying the purpose ('hierarchical organization'), but it doesn't detail parameter semantics beyond what the schema provides. With 2 parameters and partial coverage, the description compensates somewhat, earning a baseline above 3.
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 ('Set') and resource ('parent of an entity'), with the purpose of 'hierarchical organization'. It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like 'move_entity' or 'get_parent'.
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 guidance is provided on when to use this tool versus alternatives like 'move_entity' or 'get_parent', nor are any prerequisites or exclusions mentioned. The description implies usage for hierarchy management but lacks explicit context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.