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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that beyond the notion of 'unresolved conflicts', which the schema default on unresolved_only already implies. Adequate but not additive.

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 compact sentences, purpose front-loaded, no filler. Every phrase earns its place.

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?

A read-only list tool with rich annotations, a full output schema, and 100% parameter coverage needs little prose to be callable correctly. The only gap is not routing the agent between this and resolve_memory_conflict, which is a usage rather than completeness issue.

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 100% for all three parameters (limit, output_json, unresolved_only), so the schema carries the semantics. The description's mention of 'unresolved conflicts' mildly reinforces unresolved_only but adds no format, pagination, or default guidance beyond the schema.

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?

States a specific verb and resource: 'List conflicting/inconsistent memories.' That is unambiguous about what the tool returns. It does not distinguish itself from the sibling resolve_memory_conflict, which an agent could easily confuse with a listing tool, so it falls short of a 5.

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?

'Relevant when the user/admin asks to review unresolved conflicts' gives a clear trigger condition. It does not say when to prefer resolve_memory_conflict over this listing, nor does it note what to do after finding conflicts, so the exclusions/alternatives side is missing.

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