maltego_add_link

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

The description states it adds a directed link and returns a linkId, but it does not disclose behavioral traits such as whether it overwrites existing links, requires specific graph state, or has any side effects. With no annotations to fill the gap, the description is insufficient.

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 concise at two sentences with no extraneous information, but it could provide more context without sacrificing brevity. It is front-loaded with the core purpose, which is good.

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 has 5 parameters (3 required), no output schema, and no annotations, the description is too minimal. It does not explain what 'graphId' refers to, how properties are used, or the effect of adding a link. Agents need more context to use this 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 40%, but the tool description adds no parameter-level information. It does not explain the meaning of 'label' or 'properties', leaving the agent to rely solely on the schema, which has missing descriptions for these 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 action ('Add a directed link'), the resources involved ('between two entities'), and the return value ('Returns linkId'). This distinguishes it from sibling tools like maltego_add_entity, which adds an entity rather than a link.

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 maltego_add_entity or other link-related tools. There is no mention of prerequisites or conditions, leaving the agent to infer usage from the name alone.

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