read

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

The description discloses special system URIs and their return semantics ('returns active identity://default/* plus active priority=0 memories', 'reports core identity status'), defines the 'active memory' limitation, and warns not to guess URIs. With no annotations, this provides substantial behavioral context, though it stops short of explaining potential error behaviors.

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 description is compact, front-loads the primary action, and packs special cases and workflow guidance into three sentences without redundancy.

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?

Given the absence of an output schema, the description compensates by explaining what special URIs return, when to initialize, and how to handle unknown URIs. This provides a complete operational picture for a read tool.

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 schema describes 'uri' but not 'namespace' (50% coverage). The description expands on URI semantics, including exact-match requirement and special system URI formats, but does not clarify the purpose of 'namespace', leaving some ambiguity.

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 clearly states 'Read one active memory by exact URI' — a specific verb ('Read'), a resource ('memory'), and a scoping qualifier ('exact URI'). It also distinguishes itself from siblings by warning 'if URI is unknown, call search first; use list only for prefix browsing.'

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?

Explicitly provides when-to-use guidance: 'On a new session, call initialize once... then read system://boot before answering' and directs users to alternatives: 'if URI is unknown, call search first; use list only for prefix browsing.'

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