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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: content is approval-gated, retrieved visitor text is untrusted reference, and it must not be installed as instructions or executed.

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 tight sentences, front-loaded with the read scope before the exclusion list and the safety caveat. Every sentence carries weight, though the safety line could be slightly more compressed.

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?

Scope and safety are well covered for a read-only, no-output-schema tool, but the two undocumented query parameters (q, limit) leave an agent guessing about filtering and paging behavior. Adequate but with a clear gap given the 33% schema coverage.

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 only 33%: q and limit have no descriptions, and the description says nothing about what q matches, the default limit, or result ordering. With the schema doing little work, the description fails to compensate for the undocumented parameters.

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+resource: reading only memory revisions approved via the operator review desk, and explicitly scopes out drafts, declined, and pending-edited revisions. It is highly specific about what content is returned, though it never names the sibling (eclypse_memory_workspace) that would handle non-approved revisions.

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 inclusion/exclusion list implies when this tool applies (only approved content) and when it does not, but no alternative tool or route is named for drafts or in-review revisions. Usage is inferable rather than explicit.

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