erinys_link

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It says 'Create,' indicating a write operation, but does not mention idempotency, whether edges can be duplicated, whether source and target observations must exist, or any side effects.

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 concise sentence with no filler or redundancy, making it easy to parse. While it is under-specified, this dimension rewards efficient communication, and the one-liner is appropriately front-loaded.

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?

The tool has 4 parameters, no annotations, and only a one-sentence description. The presence of an output schema may cover return values, but the description still lacks usage context, behavioral details, and parameter guidance, making it insufficiently complete for safe 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?

The description says 'typed edge,' which hints that the relation parameter specifies the type, but it does not elaborate on source_id, target_id, or weight. With schema description coverage at 0%, the description adds almost no meaning beyond the parameter names themselves.

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 uses the specific verb 'Create' with a clear resource 'typed edge' and target 'observations,' making the action unambiguous. It does not explicitly contrast with sibling tools like erinys_lineage, but the phrase 'typed edge' strongly implies this is the edge-creation tool.

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?

The description provides no guidance on when to use this tool versus alternatives such as erinys_lineage or erinys_supersede. It only states what the tool does, leaving the agent to infer appropriate usage.

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