list_gallery_items

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

With no annotations, the description carries the full burden. It usefully discloses sort order (featured first, featured_rank asc, then published_at desc) and the OR-match semantics of kinds, which are genuine behavioral facts. However it says nothing about pagination behavior, result shape, or permission/visibility requirements for reading internal items.

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 short sentences: resource, then filters, then ordering semantics. Front-loaded and zero filler.

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 six-parameter, no-annotation, no-output-schema list tool, the description covers filtering and ordering but omits the returned item shape, pagination/default behavior confirmation, and access constraints. Adequate but with clear gaps.

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% and each of the six parameters is documented inline, so the baseline is 3. The description's restatement of the kinds OR-match rule duplicates the schema's own text rather than adding meaning.

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 ("List AWC Gallery items") and enumerates the filterable dimensions. It does not differentiate itself from the nearby sibling list_gallery_media, nor explain the relationship between 'items' and 'media', so an agent must infer the distinction.

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?

Filterable facets (status/kinds/featured/visibility) imply the listing use case, but there is no explicit when-to-use guidance, no mention of when to prefer list_gallery_media or a single-item getter, and no stated prerequisites.

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