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

With no annotations, the description carries the behavioral burden. It adds useful context: resolved conflicts are intentionally kept, and the record serves as evidence of not silently picking one side. This goes beyond a bare label. Still, it does not disclose output shape, pagination, safety, or authentication requirements.

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 compact and front-loaded with the core concept: conflict records. Each sentence contributes meaning, including the retention of resolved conflicts and the evidentiary purpose. It is slightly discursive but remains efficient.

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?

For a zero-parameter tool with no output schema, the description states the conceptual scope adequately. However, it does not clarify what the tool returns or how it behaves when invoked, and it offers no usage context. Given low complexity, it is acceptable but not fully 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?

The tool has zero parameters and the schema is empty, so there are no parameter semantics to document. The description reasonably focuses on meaning rather than inputs. The baseline of 4 applies because no parameter documentation is needed.

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 identifies the resource: records where sources disagree and resolved conflicts retained. It distinguishes the tool's content from siblings like gaps or unconfirmed. However, it lacks an explicit action verb like 'list' or 'show', so the operative behavior is implied rather than stated.

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 guidance on when to use this tool versus alternatives. The description implies the tool exposes conflict records, but it does not state when a user should choose jhnrd_conflicts over jhnrd_unconfirmed, jhnrd_gaps, or jhnrd_search. No exclusions or use-case conditions are provided.

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