Update a gallery

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

With no annotations, the description carries full burden and does well: discloses full-replace semantics, slug immutability, and max 200 items. Minor gap: does not explicitly state that omitting items preserves existing items, but the phrasing implies it.

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?

Three sentences, front-loaded purpose, no fluff. Each sentence earns its place: first states the action, second explains fields and full-replace, third covers constraints and workflow.

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?

Given the tool's complexity (full-replace mutation, no annotations, no output schema), the description covers the key aspects: usage, constraints, and workflow. It could mention what the response contains (e.g., updated gallery), but the instruction says that's not required without an output schema, and the core information is present.

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 coverage is 100%, but the description adds crucial semantics beyond simple field docs: full-replace behavior for items, the fetch-mutate-send workflow, and slug immutability. This is exactly the kind of value-added explanation needed.

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?

Description states 'Update a gallery by slug'—a specific verb and resource. It clearly distinguishes from siblings like get_gallery, create_gallery, and delete_gallery by focusing solely on the update operation.

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?

Provides explicit workflow guidance: 'Items is a FULL REPLACE — to add or reorder, fetch the current list with get_gallery, mutate, then send the complete new array.' Names the alternative (get_gallery) and explains when to use it, along with the immutable slug constraint.

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