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

Annotations cover only the safety flags (readOnlyHint=false, destructiveHint=true). The description adds genuinely new behavioral context beyond them: consent is required to save, moderation gates publication, secrets must not be uploaded, and no model memory is written. These are real operational constraints an agent must honor, not restatements of 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, front-loaded sentences with no filler; the domain is stated first and constraints follow. It is terse to the point of under-specification, but every sentence carries information, so the density itself is appropriate.

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?

This is a complex tool – nine actions, a nested object parameter, no output schema, and only minimal annotations. The description addresses consent and moderation but leaves 'gallery', 'pilot', 'delete_optional', and the data payload entirely unexplained, so it is not complete enough for an agent to invoke the right action confidently.

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 full burden, and it largely fails. It gestures at 'collection item' (suggesting item_id) but never explains the data object, item_id, or the opaque enum values such as 'gallery', 'pilot', and 'delete_optional'. An agent must guess what most actions consume.

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 names a domain ('private preferences and collection') and associated operations ('Read/export or delete your data'), so an agent can roughly place it in the preferences/data lifecycle. But it never states the actual verbs in the 9-value action enum, and with a null title and no sibling comparison ('continuity' vs 'account', 'session', 'catalog'), it stays vague about what this tool specifically does.

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 supplies conditional context – saving requires consent, sharing a collection item requires publish_consent plus founder moderation – which implies when certain actions are permitted. It does not, however, say when to choose this tool over siblings like eclypse_account or eclypse_session, nor which of the nine actions map to which scenario, so guidance is implied rather than explicit.

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