get_memory_with_evidence

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

No annotations provided. Description implies read operation but does not disclose auth requirements, rate limits, or behavior on missing id. Adequate but relies on default safety assumptions.

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?

Single sentence, no fluff. Every word contributes to purpose.

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?

No output schema, so description must explain return value. It mentions linked elements but lacks structure details or error behavior. Functional but leaves gaps for complex data.

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 has 0% description coverage (0/2 param descriptions). Description only clarifies 'id' as identifier but does not explain 'cwd' parameter or its optionality. Necessary context missing.

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 retrieving a single memory with linked evidence (source artifacts, quotes, provenance). Verb 'get' and resource 'memory' are explicit. Distinguishes from sibling 'get_memory' and other evidence tools.

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 when to use (need memory with evidence) but no explicit when-not or alternatives. With many sibling tools, guidance is minimal.

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