replay_timeline

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

Annotations already declare readOnlyHint=true, and description confirms read nature. Adds details on event types and return format (JSON string) beyond annotations, but omits rate limits or permission specifics.

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?

Description is four sentences plus well-structured Args and Returns sections. No filler, each sentence earns its place.

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?

With all parameters optional and annotations present, description covers key aspects (event types, time range, filters, limit). Lacks explicit output schema details, but states return type (JSON string). Could include pagination hints if applicable.

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 provides only types and defaults (0% coverage), while description explains each parameter's purpose, format (ISO timestamp, comma-separated filter), and default limit, providing substantial added value.

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?

Description uses specific verb ('Get') and resource ('full timeline of memory operations'), and lists event types covered. It distinguishes itself from siblings like replay_diff, replay_lifecycle, and replay_snapshot by being the comprehensive timeline.

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?

States prerequisite ('Requires Pro tier or Novyx Cloud') which helps the agent decide when the tool is available. Does not explicitly contrast with alternatives, but context is clear.

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