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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds real context on top: the collection is created empty, returns an ID and gallery URL, does not notify the client, needs no confirmation ("runs without asking"), and requires a Cotlet API key with app access. That is meaningful behavioral disclosure beyond the structured fields.

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 purpose is front-loaded, but the client-notification point is made three separate times ("Nothing reaches the client until you share it," "The client is not told anything until share_collection runs," "It reaches no one, so it runs without asking"). Several sentences restate the same idea, blunting conciseness.

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 simple two-parameter creation tool with no output schema, the description supplies the key missing pieces: the return values (ID and gallery URL), the no-notification behavior, and the auth requirement. Nothing critical is absent, though the redundant phrasing crowds out room for anything more specific about the created object.

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 100%, with both name and event_date fully documented in the schema, so the schema carries the semantic load. The description adds no additional parameter detail (formats, defaults, constraints), so the baseline 3 is appropriate.

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 and resource: "Creates an empty collection in your Client Gallery and returns its ID and gallery URL." It also distinguishes the creation step from the notification step carried by the sibling share_collection. The purpose is clear, though the opening sentence ("New client gallery collection") and repeated lines about client notification dilute the crispness.

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 description implies the create-then-share workflow by stating "The client is not told anything until share_collection runs," which hints at when this tool is only half the job. It never explicitly states when to call this versus other creation paths, and there are no stated prerequisites beyond the API key line.

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