memory_projection_memory

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

No annotations are provided, so the description must fully disclose behavior. It does not state whether the tool is read-only, what the projection contains, or any side effects. This is insufficient for an agent to understand its impact.

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 a single sentence, but it is under-specified rather than concise. It lacks front-loaded information about the tool's purpose and does not earn its place by providing valuable detail.

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 lack of annotations and output schema description, the description is incomplete. It does not explain the tool's output, how it differs from other memory tools, or what a 'projection' entails. This is inadequate for a tool with no parameters and no behavioral cues.

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 input schema has no parameters, so schema description coverage is 100%. The baseline is 3. The description adds no parameter semantics, but since there are none, it is acceptable.

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 'Memory-structure projection of the agent' is vague. It does not specify a clear action (e.g., 'get', 'list') or what 'projection' means. It is not a tautology but adds little clarity, especially compared to siblings like memory_query or memory_recall.

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 provided on when to use this tool versus siblings (e.g., memory_query, memory_recall, memory_projection_soul). The description gives no context about the intended use case or alternative tools.

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