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

No annotations are provided, so the description carries the behavioral burden. It clearly discloses the stateless, polling nature and indicates that it replays frames since a given sequence number, implying a read-only operation. While it could mention authentication or rate limits, the core behavioral trait (stateless polling) is well communicated.

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 extremely concise with two short sentences. The key purpose and key trait (stateless polling alternative) are front-loaded. Every word adds value, and there is no redundancy.

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?

Given the simplicity of the tool (two parameters, no output schema), the description provides sufficient context to understand when and how to use it. It covers purpose, parameter semantics, and an important behavioral trait. It could elaborate on the return format, but for a polling tool this is acceptable.

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 only 50% (only 'since' has a description), but the description adds meaningful context: 'conv' is implied to be the conversation identifier, and 'since' is explained as 'a given seq' (sequence number). This compensates for the missing schema descriptions and clarifies parameter usage.

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 clearly states the verb 'replay' and the resource 'conversation transcript frames', with a constraint 'since a given seq'. It distinguishes itself from siblings by explicitly noting it is a stateless polling alternative to a WebSocket, which is a distinct usage pattern among the sibling tools.

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 usage hint by calling itself a 'stateless polling alternative to the WS', implying it should be used when polling is preferred over real-time streaming. However, it does not explicitly compare to other sibling tools or state when not to use it, leaving the agent to infer based on context.

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