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 does disclose a useful access trait ([PUBLIC READ], no auth gate) and the underlying data source, but it omits return shape, ordering, pagination/limits, and the fact that links are filtered to active status by default — a materially important behavior left only in the schema default.

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 tight sentences with the access level front-loaded and the capability summary second. Every clause earns its place; nothing is padded.

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 a zero-required-parameter read tool with full schema coverage and no output schema, this is close to sufficient — it identifies the source of truth and the export mode. It falls slightly short on what a returned link record contains and on the default-active filtering, which the agent must discover from the schema.

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 the schema already documents rel, nodeId, status, and raw_jsonl fully. The description echoes three of the four parameter names but adds no syntax, semantics, or interaction detail (e.g. how status=all interacts with nodeId filtering) beyond what the schema supplies.

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?

States a specific verb (read/inspect) and resource (decoupled knowledge links from the canonical link ledger), and names the backing store (.braincell/map.jsonl). It is distinguishable from the sibling add_map_link by the explicit read framing, though it never names that sibling directly.

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 supported filters (nodeId, relation, raw JSONL) imply when you would reach for it, but there is no explicit statement of when to use this versus add_map_link, get_knowledge_graph, or search_knowledge. Usage is inferable rather than stated.

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