Recall

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

The description adds context about what is recalled (feedback, memories, prevention rules) and when to use it. Annotations already declare readOnlyHint=true, so the description's added value is moderate but non-contradictory.

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?

Two sentences only: first states purpose, second gives usage guidance. No wasted words, perfectly 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?

Given no output schema, the description explains the return purpose (inject past learnings) adequately. It covers purpose, usage, and parameter context, but could slightly expand on return format.

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 100% coverage for all three parameters with clear descriptions. The tool description does not add additional meaning beyond the schema, so baseline 3 is appropriate.

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 the tool recalls past feedback, memories, and prevention rules for the current task, using a specific verb and resource. It distinguishes itself from siblings like 'retrieve_lessons' by focusing on full context injection.

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 instructs to call this at the start of any task to inject past learnings, providing clear context. However, it does not mention when not to use or alternatives like 'retrieve_lessons'.

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