self_reflect

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

The description discloses a key side effect ('Saves the reflection to memory'), but lacks details on how memory is updated (overwrite/append), required permissions, or any risks. With no annotations, this is adequate but not thorough.

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?

Three sentences, no waste; front-loaded with purpose, then side effect, then usage guidance. Every sentence is valuable.

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 simple tool with 4 parameters and an output schema, the description covers purpose, side effect, and usage timing. It is fully adequate for an AI to use correctly.

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 coverage is 100%, and the description adds no parameter-specific information beyond the schema's own clear descriptions, so it meets the baseline without added value.

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 'reflect' on a 'recent interaction' to 'learn and improve', clearly distinguishing this tool from siblings like memory_save by combining reflection with memory storage.

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 explicitly advises calling 'after completing a task, especially if something went wrong', providing clear context for use, though it does not mention when to avoid or name alternatives.

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