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

No annotations are provided, so the description carries the full disclosure burden. It states it 'reads' and lists what is included, implying a safe read operation, but it does not mention any prerequisites, error behavior, or side effects. For a read tool, the description is adequate but not rich in behavioral context.

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?

The description is a single, front-loaded sentence with zero filler. It efficiently conveys the action and the key aspects of the returned data, making it easy to scan.

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 simple read tool with one parameter and no output schema or annotations, the description is largely complete. It explains what the tool returns and implies the required input. The only minor gap is not stating behavior for missing items, but this is not critical for a read operation.

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?

The schema has one required parameter, itemId, which is a UUID. The description does not mention this parameter, and schema description coverage is 0%, yet the parameter's purpose is self-evident as an identifier. The description adds no extra meaning, but the low complexity and intuitive nature of 'itemId' make this acceptable.

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 verb 'Read' and the resource 'Library item', and enumerates the content returned (content, provenance, version state, grounding availability). This distinguishes it from list/search tools implicitly through the singular 'one' and 'read' action, but it does not name a specific sibling alternative.

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 usage when you have an itemId and need full details on a single library item, but it does not explicitly state when to use this instead of list/search or mention any exclusions. The context is inferable from 'read one' but lacks explicit guidance.

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