memoryguard_history_timeline

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Read surface' implies read-only behavior, but it does not explain what a timeline contains, how results are returned, whether there is pagination, time-range filtering, or any other observable behavior. The disclosure is minimal.

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?

The description is short, but brevity here is under-specification rather than conciseness. The phrase 'V2-native read surface' contains a jargon term that is not defined and contributes no usable information. It does not earn its place in the definition.

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?

Despite having no parameters, the tool still lacks an output schema and has a highly ambiguous purpose. The description does not explain what the timeline is, how it relates to history tools, or what the agent should expect as a result. For a tool in a large sibling set, this is not enough context to select and invoke it correctly.

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?

The tool has zero parameters and the schema coverage is 100%, so there is no parameter documentation gap for the description to fill. The baseline of 4 applies because no parameters need explanation.

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 says only 'V2-native read surface.' It indicates a read operation but never identifies the resource: 'history' and 'timeline' are absent, so the agent cannot tell what data this tool actually exposes. This is too vague to count as a clear purpose, though not a pure restatement of the name.

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 about when to use this tool versus siblings such as memoryguard_history_read, memoryguard_history_search, or memoryguard_history_list_sessions. No context, exclusions, or alternative tools are mentioned, leaving the selection decision entirely to the agent.

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