Create a gallery

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses slug auto-derivation, conflict resolution with -2/-3 appending, max item limit of 200, and item shape {url, alt?}. It does not clarify behavior for explicitly provided conflicting slugs, leaving a minor gap, but the overall transparency is strong.

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 description is three sentences, front-loaded with the core purpose. Each sentence provides essential information: definition, slug behavior, item optionality, and limits. There is no fluff or redundancy, making it compact and highly readable.

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?

With 3 parameters, full schema coverage, no output schema, and no annotations, the description covers the most important aspects: creation, slug derivation, uniqueness conflicts, item limits, and item structure. It does not mention return values, but for a create tool with no output schema, this is a minor omission. It is nearly complete for the given context.

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%, giving a baseline of 3. The description adds meaning beyond the schema by explaining the slug conflict resolution behavior (-2, -3 appended) when the derived slug exists, which is not present in the schema's slug description. It also clarifies that items are optional and can be added later, reinforcing the schema's optional nature.

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 opens with a specific verb and resource: 'Create a new gallery', followed by a clear definition ('named, ordered collection of image URLs'). It distinguishes from sibling tools by explicitly referencing update_gallery for adding items later, clarifying that this tool is for creation, not modification.

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 provides explicit usage guidance: 'Items are optional at create time — start empty and add via update_gallery.' This tells the agent when to use create_gallery vs update_gallery. It also explains slug auto-derivation when omitted, but does not cover exclusions for other sibling tools (e.g., delete_gallery, list_galleries).

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