Erinys Batch Save

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

With no annotations, the description carries the full behavioral burden. 'Bulk-add' implies mutation and 'automatic similarity linking' hints at a side effect, but the description does not say whether links are always created, whether the operation is atomic, what permissions are needed, or what happens on partial failure.

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 definition is a single front-loaded sentence with no filler, but its extreme brevity leaves most of the calling contract unexplained. It is efficient but arguably under-sized for a bulk mutation with linking side effects.

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?

An output schema exists, so return values need not be described. But for a batch mutation with no annotations and an untyped item array, the description is missing critical details: item structure, auto-link behavior, and failure semantics.

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%, and the schema itself leaves 'items' as an untyped array of arbitrary objects. The description does not explain the shape of an item or clarify what auto_link controls, adding only marginal meaning beyond the field names.

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 gives a specific verb and resource ('Bulk-add observations') and mentions a distinctive behavior ('automatic similarity linking'). However, it does not differentiate this tool from the closely named sibling erinys_save, leaving the agent to infer that this is the batch variant.

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 use this instead of erinys_save, erinys_link, or erinys_reinforce. The description does not state prerequisites, batching limits, or when auto-linking should be disabled.

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