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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description's job is to add beyond that. It does: it discloses the half-open interval (from, to], that records require authentication, and that limit=0 returns only public metadata — real operational context not present in the annotations.

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 dense sentence that front-loads what is returned and appends the limit/auth caveat. No wasted wording, though the parenthetical interval notation compresses a lot into one clause.

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 usefully previews the return content (contributors, timing, record counts, added records). Missing only defaults for optional from/limit and slug format, which keeps it from being fully self-sufficient.

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 0%, so the description must carry parameter meaning. It clarifies limit semantics (cap on returned records, limit=0 = public metadata) and the from/to interval shape, but leaves slug and the default/omission behavior of 'from' and 'limit' unexplained.

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 resource and scope: the diff of appended records between two dataset versions, including contributors, timing, counts, and sample records. This distinguishes it from read_dataset/query_dataset/dataset_info, though it never names those siblings explicitly.

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?

Usage is implied by the version-to-version framing, and it notes that limit=0 yields public metadata while records need auth, which hints at two modes of use. It does not say when to prefer this over dataset_manifest or dataset_info, nor any exclusion conditions.

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