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

Annotations declare only readOnlyHint=true, and the description adds real context beyond that: the underlying endpoint (GET /api/v1/items/{item_id}), the concrete payload fields returned, and the fact that custom fields and photos are conditional on the include argument. It does not cover failure behavior for a nonexistent id, but for a read tool the disclosure is solid.

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 dense sentence front-loads the verb, resource and identifier, followed by a short endpoint reference. Every clause (returned fields, optional embeddings) carries information; the field list is slightly list-like but not wasteful.

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?

With no output schema and only two parameters, listing the returned fields is exactly the right compensating detail, and the endpoint reference grounds the behavior. Only gaps are error/not-found handling and any folder-vs-item response difference.

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 coverage is 100% and both parameters are already documented, so the baseline is 3. The description adds mild value by noting that custom field values and photos come back only 'optionally', which ties to the include enum, but it adds no format or syntax detail 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?

States a specific verb and resource ('Fetch a single item or folder by numeric id') and enumerates the returned fields, so the agent knows this is a point-read, not a list or search. It distinguishes itself implicitly from sortly_list_items/sortly_search_items via 'single' and 'numeric id', though it never names an 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?

Usage is implied rather than stated: 'by numeric id' suggests the caller must already know the id, which is the natural contrast with search_items, but neither the when-to-use condition nor any exclusion is spelled out.

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