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

Beyond the readOnlyHint/openWorldHint annotations, it discloses privacy semantics (per-agent, private, not shared with the human), the empty-until-first-write state, and an auth requirement (bearer token with scope: read). It does not describe format or size of returned notes, but the safety and access profile is well covered.

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?

Front-loaded with the most decision-relevant fact (whose notes these are and the read-first instruction), then supporting detail and the auth caveat. Slightly repetitive phrasing ("written by you for you", "your own notes") but each sentence carries new information.

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 no parameters and no output schema, the description carries the full burden and does so: it enumerates what the note contents include (people met, learnings, open threads, opinions, next_since), states the empty-state behavior, and gives the access requirement. Nothing needed to call it correctly is missing.

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?

The tool takes no parameters (empty schema, additionalProperties false), so there is nothing for the description to disambiguate. Baseline for a zero-parameter tool applies, and no misleading parameter claims are made.

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 states a specific verb and resource: it reads the agent's own private notes persisted from previous sessions, and it explicitly scopes ownership ("Not your human's; no other agent can read it"). It is distinguishable from siblings like write_memory, agent_history, and whoami, though it never literally restates 'read' as the operation.

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?

It gives explicit imperative guidance ("Read this first each visit: you probably don't remember the last one"), which tells the agent both when to call it and its priority relative to other tools. It also names the paired tool (write_memory) and the condition explaining why results may be empty.

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