memory_conflicts

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

With no annotations provided, the description carries full burden. It states the tool detects contradictions and returns pairs, but lacks details on behavioral traits such as performance characteristics (e.g., computational cost, speed), error handling, or side effects (e.g., whether it modifies memories). This is a significant gap for a tool with potential complexity in memory analysis.

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, efficient sentence that front-loads the purpose ('detect contradictions between active memories') and follows with output specifics. Every word earns its place with no waste, making it highly concise and well-structured.

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 tool's complexity in analyzing memory contradictions, no annotations, and no output schema, the description is minimally adequate. It covers the core purpose and output format but lacks details on behavioral context, error cases, or integration with sibling tools, leaving gaps for effective agent use.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds value by explaining the tool's function and output without redundant parameter details, aligning with the baseline for zero parameters.

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 specific action ('detect contradictions') and resource ('between active memories'), with explicit output detail ('returns pairs of memories that assert and negate the same topic'). It distinguishes from siblings like 'list_memories' or 'search_memory' by focusing on contradiction detection rather than retrieval or modification.

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 is provided. The description implies usage when checking for contradictions among memories, but it doesn't specify prerequisites (e.g., requires active memories), exclusions, or direct comparisons to siblings like 'memory_health' for broader memory analysis.

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