import_graph

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Import' suggests a write operation that modifies the graph, but the description doesn't mention permissions needed, whether this is a bulk operation, what happens to existing data, or any rate limits. It mentions 'various formats' but doesn't elaborate on format-specific behaviors or 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 a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a tool with 4 parameters and gets straight to the point with zero wasted text.

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 graph import tool with 4 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'import' entails operationally (does it create entities/relations?), what formats are supported beyond the schema's enum, how conflicts are resolved, or what the tool returns. The lack of behavioral context and output information creates significant gaps.

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 75% (3 of 4 parameters have descriptions), so the baseline is 3. The description adds minimal value beyond the schema - it mentions 'various formats' which aligns with the 'format' parameter's enum, but doesn't provide additional context about format requirements, data structure expectations, or practical usage of the mergeStrategy and dryRun parameters.

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 verb ('import') and resource ('knowledge graph'), specifying the action and target. It also mentions 'from various formats' which provides some scope. However, it doesn't explicitly differentiate from sibling tools like 'export_graph' or 'read_graph' beyond the directional implication of 'import' vs 'export'.

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 about when to use this tool versus alternatives. While 'import' implies data ingestion, there's no mention of prerequisites, when to choose this over other data loading methods, or how it relates to sibling tools like 'create_entities' or 'add_observations' that might handle similar data.

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