Get a collection

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the bar for additional disclosure is lower. The description adds useful context by explaining that the 'current version' feeds conflict detection for update and delete operations, which is behavior beyond the raw annotation flags.

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 sentences with no filler, and the core action is front-loaded in the first sentence. The second sentence earns its place by explaining why the version matters rather than repeating schema information.

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 single-fetch read operation, the description, full input schema, output schema, and annotations together provide everything an agent needs to invoke it correctly. The mention of version-for-conflict-detection adds the key cross-tool context, and no critical call guidance is missing.

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 the schema already documents groupId, verbose, and collectionKey with clear semantics. The description mentions fetching 'by key' and the version, but it does not need to add parameter-level detail because the schema fully covers it.

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 uses a specific verb ('Fetch') and resource ('one collection by key'), and lists what is returned: name, parent collection, item count, and current version. The singular 'one' clearly differentiates it from sibling zotero_list_collections, and naming the update/delete siblings further clarifies its role.

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?

It explicitly states that the returned version is what zotero_update_collection and zotero_delete_collection use for conflict detection, giving an agent a clear signal to fetch before mutating. It does not explicitly contrast with zotero_list_collections or state when not to use this tool, so it stops short of a full when/when-not guide.

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