vault_mem_timeline

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

No annotations are provided, so the description carries the full behavioral burden and it discloses almost nothing. It does not say the operation is read-only, how the before/after windows default or cap, what happens if the memory ID does not exist, or how the 'id' vs 'observation_id' alias is resolved when both are supplied.

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?

A single front-loaded sentence with no filler, and the key concept (chronological context around an observation) leads. It is efficient, though its brevity contributes to the coverage gaps elsewhere.

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?

For a 5-parameter tool with zero annotations and no output schema, the description leaves out the return shape (what a 'timeline' entry looks like), default window behavior, and how the two ID fields interact. An agent could call it, but could not predict what it gets back or which ID field to trust.

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 description coverage is 100%, so the schema already documents all five parameters including the before/after defaults and the alias note; the baseline of 3 applies. The description adds no additional meaning beyond the schema, and notably does not resolve the alias-precedence question.

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 states a specific verb+resource combination ('Retrieve chronological context ... around a memory observation') that clearly signals a timeline/windowing read operation. It does not differentiate itself from the near-sibling vault_mem_context, which an agent could easily confuse with this tool, so it stops short of a 5.

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?

There is no guidance on when to use this versus vault_mem_get (single observation) or vault_mem_context (broader context bundle). Nothing indicates prerequisites, or whether an observation ID must already exist. The agent must infer the selection rule entirely from the name.

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