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

Annotations already declare readOnly/idempotent/non-destructive. The description adds genuine context beyond them: replay semantics, oldest-first ordering, cursor omission behavior, and the loop-until-has_more pagination contract. Return shape is not described, but that's partly covered by the pagination guidance.

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 compact sentences, front-loaded with the primary action and immediately followed by the cursor-omission rule and pagination instruction. No filler.

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?

For a paginated read-only replay tool with no output schema, the description conveys the essential behavioral contract (ordering, cursor handling, pagination loop). It stops short of describing the change record shape, which an agent must infer from the response.

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 67%; cursor and api_key have descriptions in the schema, limit does not. The description adds the cursor-omission semantics ('omit to replay from start') which supplements the schema meaningfully, but says nothing about limit's role beyond the maximum=50 already given.

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+resource: replay committed activity after a cursor. Distinguishes itself from read_change_history and list_contributions with the 'without missions' scoping phrase. Could be more explicit about what 'activity' entails (a journal of changes), leaving mild ambiguity.

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?

Gives clear usage conditions — omit cursor to replay from start, follow next_call until pagination.has_more is false. Does not explicitly name alternatives (e.g., read_change_history), but the operational flow is well specified.

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