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

The readOnlyHint annotation already signals a safe read operation. The description adds only the REST endpoint (GET /collections/{collectionId}), which provides minor technical context but does not disclose additional behavioral traits such as response structure, error handling, or prerequisites beyond the ID. The annotation covers the main safety aspect, so a baseline score is appropriate.

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 remarkably concise, consisting of two short sentences. The first sentence states the core purpose, and the second provides the REST endpoint. Every word contributes value with no redundancy or fluff.

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?

This is a simple read tool with a single parameter and no output schema. The description sufficiently conveys the operation and the necessary input (collection ID). However, it does not mention potential return values or edge cases like 404 responses, but given the simplicity and annotation support, the context is adequately 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?

The input schema provides a 100% description coverage with the single parameter 'collectionId' described as 'The collection id.' The tool description does not add any extra meaning or format details beyond what the schema already contains, so the baseline score of 3 applies.

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 purpose: 'Get a collection by its ID.' The verb 'Get' and resource 'collection' are specific, and the qualifier 'by its ID' differentiates this from sibling tools like list_collections, which would retrieve multiple collections.

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 implicit usage guidance by indicating the tool is for retrieving a single collection when its ID is known. However, it does not explicitly mention alternatives or scenarios where this tool should not be used, such as needing to list all collections, which would require list_collections.

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