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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds a scoping detail ('owner-private', 'in a workspace') that hints at access restrictions, but it does not elaborate on what happens for non-owner-private items or workspace resolution.

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?

A single sentence that front-loads the verb and object, with no filler. Every word contributes meaning, and the sentence is immediately parseable.

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 simple read operation, annotations, and output schema, the description is adequate for basic invocation but leaves the term 'owner-private' and workspace default behavior unexplained. It does not reference sibling tools for locating an item_id before reading.

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%, with workspace_id and workspace_name already explained in the schema; item_id is self-explanatory from the tool name. The description adds no additional parameter context, so it neither helps nor hurts beyond the schema.

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 ('Read') with a precisely scoped resource ('one owner-private Collect+ item') and a location ('in a workspace'). It clearly differentiates this tool from sibling read tools like read_document or read_note, and from list_collectplus_items via the singular 'one'.

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 implies this tool is for retrieving a single known Collect+ item, but it does not state when to prefer it over list_collectplus_items or search_collectplus_items, nor does it explain the 'owner-private' precondition. Usage guidance is present only by implication.

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