hippocampus_write_reflection

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

No annotations are supplied, so the description must disclose behavioral traits. It gives a metaphorical analogy (prefrontal cortex) but does not specify operational effects such as whether the event must exist, whether reflections are overwritten, or any required permissions.

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 concise at two sentences, but the second sentence's metaphorical framing ('prefrontal cortex...') adds little operational value. Still, it is short and front-loaded.

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?

This tool requires a nested object and all parameters are required, yet there is no output schema or annotations. The description does not explain how reflections relate to events or the broader memory system, leaving significant gaps for correct invocation.

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 description does not mention any parameters, adding no meaning beyond the input schema. With schema coverage at 67%, the description could have clarified event_id or reflection structure but does not.

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?

Description states 'Create agent-relative Reflection about an event,' providing a specific verb (Create) and resource (agent-relative Reflection). The 'egocentric perspective' phrasing distinguishes it from hippocampus_write_event, which likely records objective event details.

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 explicit when-to-use or alternative guidance is provided. The description implies usage when creating a reflection about an event but does not contrast with siblings like hippocampus_write_event or encode_memory.

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