memory_conflicts

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

With no annotations, the description carries the behavioral burden. It conveys that this is a read/heuristic operation ('Find possible conflicting memories') and hints at non-determinism with 'possible', but it does not disclose whether results are tentative, whether it performs any state changes, or how conflicts are ranked or returned. However, the simple read-only nature is largely inferable.

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 focused sentence that front-loads the verb and resource, then adds the two key conflict categories. There is no redundancy, and every word contributes to understanding the tool's purpose.

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: one optional parameter and an output schema is present, so return value documentation is covered. However, the absence of usage guidance and any parameter semantics leaves just enough ambiguity that the description is minimally viable rather than complete.

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 0%, and the description does not mention the 'limit' parameter at all. The schema only shows it is an integer with a default of 50, leaving its meaning and effect on the conflict-finding behavior completely undocumented.

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 uses a specific verb ('Find') and a specific resource ('possible conflicting memories'), and enumerates the two categories it covers: duplicate facts and personal-memory contradictions. This distinguishes it clearly from the many sibling memory tools, especially listing and retrieval tools.

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?

The description does not state when to prefer this tool over alternatives, nor does it mention any exclusions. While the purpose implies it is for surfacing conflicts, an agent is given no guidance about how it relates to memory_review, memory_personal_review, memory_probe, or other analysis-oriented siblings.

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