memory_relate

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

Discloses bidirectional querying but directional storage, which is useful. No annotations provided, so description bears full burden; however, it omits side effects, permissions, or implications like idempotency or overwrites.

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, concise and front-loaded with purpose. No redundant information.

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?

Lacks description of return value (no output schema). For a creation tool with 5 parameters, details on what is returned upon success or failure are missing. Adequate for basic understanding but not fully self-contained.

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 covers 80% of parameters with descriptions. The description adds minimal parameter insight beyond the schema; the example is helpful but does not clarify optional parameters like 'strength' or 'context' beyond their schema definitions.

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?

Clearly states the tool creates a relationship between two entities with an example ("Amin builds ModQuote"). Differentiates from siblings like memory_observe and memory_entities by focusing on relational creation.

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 guidance on when to use this tool versus alternatives (e.g., memory_observe for observations, memory_entities for entity creation). Lacks context about prerequisites or when not to use.

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