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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered elsewhere. The description does add genuine context beyond that: access is anonymous (no registration or purchase) and the catalogue reflects 'current access and payment availability', implying live/authoritative data. It stops short of describing what a response contains or whether listings are paginated.

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 short sentences, purpose first, prerequisites last – well front-loaded with no filler. Minor deduction for jargon-heavy noun stacking ('human deliberate-memory product', 'operator research pilot') that consumes space without resolving meaning.

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 zero-required-parameter read with annotations and no output schema, the description establishes purpose, anonymity, and data freshness. What it never resolves is what the agent will actually receive – a list of products, prices, or availability flags – leaving the caller unable to predict the response shape.

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?

Only one optional parameter (account_ref) exists and its schema description covers it at 100%, including the reuse/omit guidance, so the schema does the work. The tool description adds nothing about the parameter, which is acceptable at this baseline.

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 verb+resource pair ('Read ... catalogue') is present and the sentence enumerates the offering types covered: product, free personal notebook, research pilot, sanctuary catalogue. However, phrases like 'human deliberate-memory product' and 'sanctuary catalogue' are opaque jargon, and the description never contrasts itself with any of the ~36 sibling eclypse_* tools, so an agent cannot tell whether this is the discovery entry point, a pricing page, or a content index.

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?

The only guidance is a precondition ('Reading requires no registration or purchase'), which tells the agent nothing about when to reach for this versus eclypse_private_access, eclypse_preview, eclypse_terms or eclypse_guest_checkout. There is no when-to-use, no when-not-to-use, and no named alternative.

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