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

With no annotations, the description carries the full burden. It discloses that the page is finite, that events are retained, and that source freshness fields are preserved, which are useful behavioral traits. Yet it omits details such as pagination behavior, ordering, error conditions, or return format, leaving gaps in transparency.

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 a single, front-loaded sentence with no wasted words. It conveys the core purpose and a usage hint efficiently. However, the heavy use of jargon ('Redis stream id', 'source freshness fields') makes it slightly less accessible than a fully plain-language description.

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?

The tool has three optional parameters, no output schema, and no annotations, yet the description does not cover parameter semantics, return format, or operational details. It mentions the reconnect scenario but leaves too much unspecified for an agent to reliably invoke it without additional context.

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 0%, and the description fails to explain any of the three parameters. The only hint is 'after a Redis stream id', which likely maps to the 'since' parameter, but no explicit mapping or meaning is given for 'limit' or 'symbols'. This is a significant gap.

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 identifies the tool as a 'Finite catch-up page for retained market events after a Redis stream id', which clearly states the function (retrieve a finite page) and the resource (retained market events). It also implies usage for stream recovery, but it does not explicitly contrast with the sibling streaming tools, so it stops short of full differentiation.

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?

The description provides a specific usage context: 'use after reconnect'. This is a clear signal for when to invoke the tool. However, it does not explicitly state when not to use it or name alternative tools for live streaming or historical queries, so it lacks explicit exclusions.

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