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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered; the description earns credit for adding behavior they cannot express — the owner-only access rule for drafts and the fact that the returned payload differs by publication state. It does not mention pagination, size limits, or errors for a missing/unauthorized dataset, which keeps it from 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?

A single front-loaded sentence opening with the verb and resource, with parentheticals used to enumerate payloads rather than pad. It is dense to the point of being telegraphic in places ('config, configVersion, preview'), but no sentence is wasted.

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 two-parameter read tool with full schema coverage, an output schema, and annotations covering the safety profile, the description supplies the missing piece — access rules and payload variation by dataset state. Only edge-case behavior (errors, empty history) is left unaddressed, a minor gap.

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 both parameters are already documented, including that 'revision' must be a published revision and that omitting it yields the current one. The description only restates this as 'Optional revision reads history,' adding the nuance that it selects historical state but no new syntax or format detail; baseline 3 applies.

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 ('Read a dataset') and immediately splits the resource by state: a published dataset readable by anybody vs. a draft readable only by its owner, naming the payload in each case (snapshot + freshness + default result vs. config, configVersion, preview). That is enough for an agent to tell this apart from siblings like atlas_dataset_changes without opening a 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?

Gives clear context for when the call succeeds: published datasets are open to anyone, drafts require ownership, and passing 'revision' switches to a history read. It does not explicitly route to or exclude an alternative sibling (e.g., atlas_dataset_changes for change history), so it stops short of full when/when-not guidance.

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