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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restatement. The description adds two useful behavioral facts beyond the annotations: results are ranked by research-item count and carry catalogue links, but says nothing about pagination behavior or result size limits.

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?

Two short sentences, front-loaded with what the tool returns and followed by the downstream chaining hint. No filler, though the second sentence is a usage note rather than a structural necessity.

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 partly compensates by naming the ranking criterion and catalogue links, but it omits the shape of returned items (what fields, what the links look like) and leaves offset semantics undocumented. Adequate but with clear gaps for a list tool with three parameters.

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 67%; limit and keyword are documented in-schema, while offset is not described anywhere. The description itself adds no parameter meaning beyond what the schema provides, so the baseline 3 for high-but-incomplete coverage 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+resource ('Omeka item sets') and adds scope detail (ranked by research-item count, with catalogue links), which helps distinguish it from sibling listers like list_categories or list_subjects. It does not explicitly contrast with compare_collections or get_collection_overview, so it falls short of a 5.

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 second sentence gives forward guidance ('Feed an ID into search_research_items.collection'), which tells the agent what this list feeds into, but it never says when to use this tool versus siblings such as compare_collections or get_collection_overview. Usage is only implied by the ranking/filtering framing.

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