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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: results are ranked by item count and each entry carries a browsable page. Pagination behavior for limit/offset is not mentioned.

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?

Front-loads the verb and resource, uses an em-dash aside for the taxonomy, and closes with the actionable routing sentence. The middle enumeration of collection types is slightly padded but each item is genuinely informative.

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 no output schema, the description does describe returns (item-count ranking, browsable page per collection), which is the key missing piece an agent would otherwise lack. Only the offset parameter and pagination semantics are left unexplained.

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 67% (limit and keyword documented, offset undocumented). The description adds nothing about any of the three parameters, so it neither compensates for the offset gap nor clarifies ranking interaction with limit. Baseline 3 is appropriate given the schema does most of the work.

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 (list) and resource (collections), then defines the domain term precisely as Omeka item sets with the three subtypes it covers (project collections, external archives, curated sets). It is clear an agent is enumerating collections, but it never explicitly distinguishes itself from sibling get_collection_overview, which an agent would need in order to pick correctly between the two.

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?

Gives concrete downstream guidance: feed a title or id into the `collection` filter of search_research_items, which tells the agent this is a discovery/lookup step in a larger workflow. No exclusions or explicit 'do not use when' conditions, and listing vs. single-collection detail is left implicit.

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