list_changes

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds two useful behavioral qualifiers beyond that: only "published" changes are returned and only for a "visible" carrier, which signals an access restriction. It still omits pagination behavior, how filters combine, and what a change record looks like.

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?

A single front-loaded sentence with no filler, which is structurally clean. But it is under-specified rather than concise for a six-parameter tool, so the brevity costs the agent necessary information rather than saving it.

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?

With six optional parameters, no output schema, and zero schema description coverage, an agent needs the description to explain filtering, pagination via cursor/limit, and the since/event_types semantics. None of that is present, so the definition is not adequate for the tool's complexity.

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% across six parameters, so the description carries the full burden and fails it: limit, since, usdot, cursor, event_types, and watchlist_id are never mentioned or explained. Worse, "one visible carrier" implies a carrier identifier is required, yet no parameter is marked required, leaving the agent unable to resolve how to target the carrier.

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 names a verb ("Read") and a resource ("published material changes") scoped to "one visible carrier," so the general intent is inferable. However, "material changes" is undefined jargon and nothing distinguishes this from siblings like list_watch_events or get_evidence, which plausibly return overlapping change/event data.

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?

There is no statement of when to use this instead of list_watch_events, get_evidence, or get_latest_edition, and no prerequisites or exclusions are given. The phrase "one visible carrier" implies carrier scoping but never says whether usdot, watchlist_id, or neither must be supplied.

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