memory.link

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It does not state whether links are directional, whether duplicates are rejected or silently merged, whether invalid ids error, or whether the relation is symmetric. For a mutation tool with zero annotation coverage, this is a substantial gap.

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?

A single short sentence with no wasted words, so it is concise. The brevity comes at the cost of under-specification rather than tight editing, leaving it merely adequate.

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?

A three-parameter mutation tool with no annotations, no output schema, and 0% parameter documentation needs far more than one sentence. Missing are directionality of the link, duplicate/error behavior, and the meaning or availability of the relation types, all of which an agent needs to invoke 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 and does not: fromId, toId, and relation are never explained. The phrase 'between two patterns' hints at two endpoints but gives no directionality semantics, which matters for asymmetric relations like depends_on or evolved_from. The six enum values in the schema carry the relation meaning entirely on their own.

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 names a clear verb ('Create') and resource ('relationship between two patterns'), so the basic operation is identifiable. However, 'patterns' is never defined, and it does not distinguish itself from sibling memory.related, which presumably reads the same relationships. Purpose is stated but non-specific about what a 'pattern' is or how this differs from related tools.

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?

There is no guidance on when to create a link versus when to read existing links (memory.related) or evolve/store patterns. No prerequisites, no mention of what happens if the relationship already exists. The agent must infer all usage context from the tool name alone.

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