trailmem_link

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

No annotations are provided, so the description carries the full burden. It discloses the creation/removal actions and edge types, but lacks details on side effects, idempotency, permissions, or behavior when edges already exist.

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?

Two sentences front-load the core functionality and list edge types. It is efficient but could be slightly more compact by integrating the type list into the first sentence.

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?

With 6 parameters and moderate complexity, the description lacks details on return values, error handling, and validation. It assumes prior knowledge of trailmem_show for removal, leaving gaps in completeness.

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 has 0% description coverage. The description explains the roles of action, source, target, edge_type, and edge_id, but omits metadata. It adds meaningful semantics beyond the schema for most parameters, though not comprehensively.

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 it creates or removes a typed edge between memories, specifying verb and resource. It distinguishes between two actions and mentions a sibling tool (trailmem_show) for removal, but lacks explicit differentiation from all siblings.

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 explains when to use 'add' vs 'remove' and references trailmem_show for removal, but does not provide when-not-to-use guidance or contrast with other siblings like trailmem_edit or trailmem_store.

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