trailmem_show

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

Discloses that it returns edges and that edge IDs are used by other tools (link remove). No annotations provided, so description carries burden; it implies read-only behavior but does not state explicit side effects.

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, no fluff. Front-loaded with core purpose and key differentiator.

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?

Describes output well (content, edges, supersede chain), but lacks parameter description. With output schema existing, return values are covered, but input parameter 'ref' is unexplained.

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 coverage is 0% and description does not explain the 'ref' parameter. The agent cannot infer what value to provide (e.g., memory ID, reference string).

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 it fetches a full memory with content, edges, and supersede chain. Distinguishes from siblings by being the only tool that returns edges, which are needed for link remove.

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 use when you need to retrieve a full memory with edges. Does not explicitly state when not to use, but differentiates from siblings by mentioning edge retrieval.

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