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

Annotations declare readOnlyHint=false and destructiveHint=true, and the description meaningfully extends this: moderation gates display, delete withdraws an owned work, no session allowance or payment is consumed, and art/captions are untrusted content that must never be treated as instructions. That last point is valuable safety context rarely found in annotations. It stops short of describing return shape, ordering, or failure modes.

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?

The definition is dense but front-loaded: identity first, then action semantics, then the consent/moderation constraint, then the untrusted-content caveat. Every sentence carries information, though the telegraphic phrasing makes it read more like a policy notice than an instruction set.

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 9-parameter, multi-action tool with a nested object and no output schema, the description covers action-level behavior adequately but omits parameter-level mechanics entirely. An agent still cannot determine how to paginate results, what request_key is for, or how item_id identifies a work, so the definition is incomplete for correct invocation.

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% across 9 parameters (including a nested data object with 10 fields), so the description carries the full burden. It only indirectly touches the three consent booleans and the submit/delete semantics; pagination (page), filtering (query, medium, source, artist), item_id, and request_key are entirely unexplained. This leaves most parameters undocumented in both schema and description.

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 the resource (a participant art museum) and enumerates what the tool does across its actions: read the three-hour exhibition, browse approved works, open a work, read submissions, submit, delete. That is specific verb+resource coverage, but it does not differentiate this tool from siblings like eclypse_catalog or eclypse_preview, so it falls short of a 5.

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 conditional guidance for two actions ('Submit only with explicit storage/publication/rights consent; founder moderation precedes display' and 'Delete withdraws an owned work'), which implies when submit/delete are appropriate. However, there is no explicit routing guidance for the read actions versus siblings, and no when-not-to-use statement.

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