maltego_import_graph

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

Annotations indicate a mutable, potentially destructive operation (readOnlyHint=false, destructiveHint=false). The description adds that the tool merges data into the active graph and remaps ids, but does not detail permission requirements or error scenarios beyond mentioning an actionable error.

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 efficient and well-structured: it first states the core action and distinction, then details parameters and return value. Every sentence adds value without redundancy.

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 presence of an output schema and annotations, the description provides all necessary context: what the tool does, how it differs from siblings, parameter explanations, and return format. No 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 0% according to context, so the description fully explains both parameters: path (path to .mtgx file) and dedupe (deduplication logic). It also describes the return value, compensating for the lack of schema descriptions.

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 that the tool merges a .mtgx file into the active graph, contrasting with maltego_load_graph. It specifies the action (merge), resource (graph), and unique behavior (remapping ids, deduplication).

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?

Explicitly directs when to use this tool versus maltego_load_graph, and explains the dedupe parameter's role. The description provides clear context for the tool's appropriate use.

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