The archive in one query: merged, year-sorted events (graduations, exhibitions, press, publications) between two years. Great for a chronological overview of Estonian jewellery art.
| Name | Required | Description | Default |
|---|---|---|---|
| to_year | Yes | ||
| from_year | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint and openWorldHint. The description adds behavioral details about merging event types and sorting by year, enhancing understanding beyond annotations.
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 concise sentences: first defines the action and output, second gives a use case. No unnecessary words.
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 simplicity (two parameters, no output schema), the description adequately explains purpose, scope, and event types. Could mention if events are inclusive of both years, but overall complete.
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?
Parameter description coverage is 0%. The description implies the two integer parameters represent a year range but does not specify inclusiveness, bounds, or format. Partial compensation for lack of schema descriptions.
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 clearly states the tool's function: 'merged, year-sorted events between two years' with specific event types. It distinguishes from sibling tools that focus on individual entities or searches.
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 clear context for use ('Great for a chronological overview of Estonian jewellery art'), but does not explicitly mention when not to use or list alternatives, though siblings are available.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a unique entity or action (e.g., get_artist vs. search_artists, get_relations vs. get_stats). No two tools have overlapping purposes, so an agent can clearly distinguish them.
All tools follow a consistent verb_noun pattern: either get_<entity> or search_<entity>. No mixing of conventions like camelCase or different verbs.
12 tools is well-scoped for an archive server covering artists, exhibitions, works, organizations, marks, press, and graph relations. Each tool earns its place without redundancy.
The tool surface covers the main entities (artists, works, exhibitions, organizations) and provides search and retrieval for all key types. Additional tools like get_relations and get_timeline fill gaps for connected data and chronology, making the set feel complete for its domain.