Enhanced Knowledge Graph Memory Server

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits like whether it's read-only (implied by 'Get' but not explicit), pagination, rate limits, permissions needed, or what happens with invalid inputs. This is inadequate for a tool with potential complexity in graph traversal.

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 with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every part earns its place by conveying the essential 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 no annotations, 0% schema coverage, no output schema, and complexity from graph operations, the description is incomplete. It doesn't cover return format (e.g., list structure, depth), error handling, or how 'descendant' is defined (e.g., recursive children). This leaves significant gaps for an AI agent to use it correctly.

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 0%, so the description must compensate but adds no parameter details. It mentions 'entityName' implicitly but doesn't explain what it expects (e.g., format, valid values, or if it's case-sensitive). With 1 required parameter and no schema help, this leaves semantics unclear.

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 'Get all descendant entities of an entity' clearly states the verb ('Get') and resource ('descendant entities'), but it's vague about scope and doesn't differentiate from siblings like 'get_children' or 'get_subtree'. It specifies 'all' which adds some clarity, but lacks detail on what constitutes a descendant.

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 such as 'get_children' (immediate children only) or 'get_subtree' (might include the entity itself). The description implies a hierarchical traversal but doesn't specify depth or exclusions, leaving usage context unclear.

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