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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value with the permission note ('any role can read') and the shape of each change record (path, rev, actor, kind, deleted), plus a note that the current rev is returned. It stops short of pagination or ordering guarantees, so not a 5.

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?

Three sentences, front-loaded with what it returns and immediately followed by the read_file routing. Dense with information and no filler, though the return-fields enumeration mid-sentence slightly slows the lead.

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 no output schema, the description correctly fills the gap by enumerating the returned change fields and noting the current rev is included. Combined with the parenthetical about access, an agent has enough to call it correctly. Ordering/pagination semantics remain unstated.

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%, so both parameters (`id` and `rev`) rely on name inference. The description implies `id` is the artifact and `rev` is a baseline revision, which helps, but it never states accepted rev format or whether the given rev is included/excluded from results. It partially compensates but leaves real ambiguity.

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 opens with a specific verb and resource ('List the file paths of an artifact that changed after a revision'), and immediately distinguishes itself from read_file ('Returns paths only; call read_file for content'). An agent can tell exactly what it returns without opening the schema.

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?

It gives a clear when-to-use ('to catch up on human edits made since the rev you last saw') and routes content retrieval to a named sibling. There is no explicit when-not or prerequisite guidance beyond this, but the usage context is unambiguous.

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