create_relations

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, so the description need not restate the safety profile. What it adds instead is mostly non-actionable ('backed by the same v2 SQLite store') or off-topic — the sentence about logical deletion and retained history describes delete_relations behavior, not a create operation. Nothing is said about what happens on duplicate or conflicting relations, or about partial failure in a batch, which is the real behavioral risk here.

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?

Three short sentences with little padding, so it is not bloated. But it is poorly front-loaded: the leading sentence is provenance trivia rather than the operation, and the final sentence concerns a different tool family entirely. Structure wastes the position of highest attention.

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?

This is a mutating batch tool with no output schema, no annotation coverage of semantics, and a fully undocumented nested parameter. The definition should at minimum say what a relation is, whether endpoints must pre-exist, and what a successful response confirms; it says none of that. An agent could call it, but could not call it correctly with confidence.

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 single parameter is a nested array of objects with from/to/relationType, none of which is explained in the description. The description provides no meaning for these fields, no note that up to 100 relations can be submitted per call, and no guidance on valid relationType values. With zero coverage in the schema, the description had the full burden and did not carry it.

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 never states that this tool creates relations between entities; it only labels itself a 'compatibility tool backed by the same v2 SQLite store'. The actual verb+resource pairing exists only in the name, so an agent must infer the purpose rather than read it. It does hint at being a legacy analog of newer memory tools, but that is context, not a statement of what it does.

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?

'New callers should prefer versioned native memory tools' is a genuine when-not-to-use signal, which is more than most definitions offer. However, it never names the concrete alternative among the many siblings (create_entities, remember_memory, add_observations), so the agent cannot route deterministically. There is also no statement of prerequisites, such as whether the referenced entities must already exist.

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