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

Annotations already establish readOnly/idempotent/non-destructive, so the safety bar is met elsewhere. The description adds genuinely new behavior: the authorization boundary (owner-only drafts) and the fact that supplying revision switches the call to a history read rather than a current-state read.

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?

One sentence, front-loaded with the verb and resource, with parentheticals enumerating returned fields rather than padding. Dense but every clause carries information; the parenthetical nesting is slightly hard to parse on first read.

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 an output schema, the access rules and revision semantics are the only things an agent must know, and both are present. Return values are additionally described despite the output schema existing, so nothing material is missing.

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 the description carries the burden. It explains the non-obvious parameter, revision, as triggering a history read, which is real added meaning; datasetId is self-evident from the tool name. It does not explain revision format or which value means latest, so not a 5.

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?

Names a specific verb (Read) and resource (dataset), then spells out what is returned in each access case: a published snapshot with freshness and default result, or a draft's config/configVersion/preview. That content-level detail cleanly separates it from atlas_dataset_create/update/publish/archive siblings.

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?

States an implicit when-not condition: drafts are readable 'only by its owner', while published datasets are readable by anybody. That tells the agent when the call will succeed. It never names a sibling alternative or an explicit exclusion, so it falls short of a 5.

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