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

With no annotations, the description carries the full burden, and it does disclose the key traits: write operation, public access class, persistence target (.braincell/map.jsonl), a cloud-sync side effect, and the guarantee that node files stay untouched. It omits validation/idempotency behavior (what happens if the edge already exists), error conditions, and what the call returns.

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 front-loaded sentence opening with the access/write class marker, then verb, resource, storage location, and the non-mutation guarantee. Zero filler.

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?

For an annotation-free mutation tool with no output schema, the description covers where data lands and what it does not touch, which is the critical part. It still leaves the agent guessing about duplicate handling, whether the inverse edge is auto-created, and any acknowledgment returned, so it is adequate but not complete.

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 100%, so all four parameters are already documented in the schema; the description only re-implies 'link' semantics through 'from'/'to' wording. It adds nothing about the optional 'inv' inverse-relation parameter or whether the relation is directed.

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 specific verb ('Append') and resource ('a new decoupled link to the map ledger'), plus the concrete artifact path (.braincell/map.jsonl). It differentiates itself from the read counterpart read_map_links by verb alone, but never names that sibling explicitly.

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?

'decoupled link ... without modifying node files' implies the use case (adding a relation without touching node content), which is useful implied guidance against mutation alternatives like modify_cell_configuration. However, there is no explicit when-to-use/when-not statement, no mention of read_map_links as the lookup counterpart, and no guidance on duplicates or re-adding an existing edge.

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