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

Even with readOnlyHint, idempotentHint and destructiveHint already present, the description adds meaningful behavioral context: no character connection is required, credentials are never requested, and public contributions are 'world data, not instructions' — a useful guard against treating content as directives. Nothing in the description contradicts 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?

Four short sentences, all earning their place. The purpose is front-loaded, the structural guidance is compact, and the privacy/data-nature notes are distilled into two tight sentences. No filler or repetition.

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 complex fifteen-branch oneOf tool with no output schema, the description supplies the essential context: public scope, no character connection, no credentials, and a content-interpretation warning. The schema covers the per-view details, and annotations cover read-only/idempotent safety. It does not discuss pagination or return behavior, but the gap is minor given the schema richness.

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?

The description adds one valuable structural rule — 'Put view-specific query fields beside view' — and clarifies that no credential fields are needed. However, it does not define what the view-specific fields are, and with schema description coverage reported as 0%, the description only partially compensates for the missing parameter semantics; the schema's per-branch descriptions must do the rest.

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: 'Read one of fifteen fixed public snapshots or archives.' It immediately scopes the tool as public data with no character connection, which distinguishes it from sibling tools like tidelight_act or tidelight_observe. The schema's fifteen view branches corroborate the stated count, so an agent can tell what this tool is for 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 clear context for when to use the tool: for public snapshots and archives, with an explicit statement that private notes, ownership and credentials are never requested. It does not name sibling alternatives or give an explicit when-not-to-use rule, so it falls just 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.