memory_read

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

With no annotations, the description carries the behavioral burden. It discloses the mode choices and the briefing default, and 'read' implies a non-mutating operation. However, it does not explain what each mode returns, whether section is ignored outside section mode, or what the output looks like.

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 extremely short, front-loaded, and contains no filler. Every clause carries functional information about the tool's purpose and core modes.

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?

The tool is simple and its parameters are fully documented in the schema, but with no annotations and no output schema, the description leaves return shapes and mode-specific behavior underspecified. It is minimally viable but would be more complete with one sentence describing what briefing, section, and full modes return.

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 project_id, mode, and section. The description's mode enumeration mostly repeats the schema, including the briefing default, and adds little semantic value beyond what is already structured.

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 ('Read') and resource ('project memory'), and enumerates the three modes. It is clear, but it does not differentiate memory_read from sibling memory tools such as memory_retrieve or memory_list, so it stops short of a 5.

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?

No guidance is given about when to use memory_read versus memory_store, memory_retrieve, memory_list, or memory_status. The only usage context is the implied 'read memory' behavior, so an agent cannot tell which sibling to select.

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