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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds genuine context: quotas (500 records, five versions, 5 MB) and that reading/export/deletion remain free after expiry. It does not say which of the nine actions are destructive or whether consent/accept_terms gating is required, leaving the most consequential behavior undisclosed.

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 dense sentences with no filler, but the lead is an unexplained fragment ('Private continuity: 500 records...') and the content is ordered by policy/limits rather than by what the agent needs first. Reasonably sized for the amount of policy it conveys, yet not front-loaded around the tool's function.

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 16-parameter, 9-action, mutation-capable tool with no output schema and near-zero schema descriptions, the description covers quotas and billing but omits the action space, required vs optional parameters, and any return behavior. An agent cannot assemble a correct call from this text alone.

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 6% across 16 parameters, so the description must compensate and largely fails to. Hints like 'explicit current-revision writes' and '100-credit balance' loosely gesture at revision and spend_paid_credits, but title, tag, tags, query, page, kind, due, consent, accept_terms, request_key, record_id and data are entirely unexplained.

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 frames the tool as 'Private continuity' with limits and pricing, and obliquely names capabilities (search, current-revision writes, reading, export, deletion). It never states the core purpose — managing a private memory workspace across nine actions — as a clear verb+resource. Sibling tools like eclypse_continuity and eclypse_approved_memory are never distinguished.

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?

One useful routing hint exists ('The legacy activate action redeems only an existing 100-credit balance; it is not a new credit sale'), separating activate from purchasing. Otherwise there is no guidance on when to use search vs read vs versions vs save, nor which actions private continuity affords over the sibling memory tools.

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