memora

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

No annotations provided, so description carries full burden. Discloses critical 300s rate limit and global scope ('all memories'), indicating heavy operation. Could clarify if destructive or additive, and whether it blocks other memory operations.

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 with zero waste. Purpose front-loaded, rate limit follows as secondary operational constraint. Perfect density.

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?

Adequate for a parameterless tool with output schema available. Rate limit warning is essential for a global rebuild operation. Could mention safety implications (e.g., 'safe to run live') but covers the critical invocation constraint.

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?

Zero parameters per schema, earning baseline score of 4. No parameters to document.

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?

Specific verb 'Recompute' with clear resource 'cross-reference links' and scope 'all memories'. Distinct from sibling memory_link (manual) and memory_rebuild_embeddings (different data type).

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?

Implies heavy usage via '300s cooldown' rate limit warning, but lacks explicit guidance on when to invoke (e.g., 'run after bulk imports' or 'use instead of manual linking when...'). No comparison to memory_link or memory_related.

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