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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description adds genuinely new behavioral context: that the listing is 'compact' and, importantly, that it does NOT establish verified integrity or real-AI eligibility, warning the agent against over-reading results.

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?

Two tight sentences with no padding, and the core purpose ('read a compact public terminal-session catalog') is front-loaded before the caveat. Efficient and well-ordered.

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?

No output schema exists, but 'compact public terminal-session catalog' plus the negative caveat give an adequate sense of what comes back, and both optional params are fully schema-documented. The only minor gap is return shape detail for the catalog entries themselves.

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%: limit and offset are fully documented in the schema, including the note that offset snapshots may change between calls. The description adds no parameter-level detail beyond that, so the baseline of 3 is appropriate.

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?

States a specific verb (read) and resource (compact public terminal-session catalog), which is enough for an agent to identify it as a listing tool. It hints at the boundary with play_replay, but does not fully name the differentiation, so it falls short of a clean 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?

The sentence 'play_replay checks one complete replay' implies an alternative and the condition that separates listing from verification, but it never states explicitly when to reach for public_replays versus its siblings. Usage is inferable rather than stated.

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