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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context beyond that: sequence ordering, newest-page default, and next_since_seq as the continuation position. It does not describe rate limits or filtering behavior, but the core operational semantics are clear.

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?

Four sentences, each front-loaded and purposeful: purpose, sync usage, pagination default, and alternatives. No redundant or filler wording.

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?

An output schema exists, so the description need not explain return values in detail. It covers sequencing, pagination continuation, default behavior, and alternative tools, which is complete for a change-feed synchronization tool.

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 100%, so the schema already documents limit, since_seq, and entity_type. The description adds meaning around since_seq pagination and continuation, but it does not elaborate on limit or entity_type, so it remains at the baseline level for parameter semantics.

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 and resource: return record change events in sequence order. It also distinguishes itself from siblings by naming get_freshness and get_record with their distinct roles, so an agent can select it without opening other schemas.

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 explicit usage conditions: synchronize data after since_seq, use 0 for full history, omit since_seq for the newest page. It also names alternatives for adjacent needs (get_freshness for import times, get_record with as_of_seq for historical records).

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