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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered; the closing "Reads only" merely confirms it. The description earns credit for disclosing what actually comes back (every value plus file path, and in locale mode the translation file, its state, and which fields still lack a translation) — genuinely useful since no output schema exists.

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, front-loaded with the core read operation and its return shape, with the locale mode clearly conditioned. The second sentence is a dense run-on list, but every clause carries information and nothing is padded.

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 read tool with no output schema, the description covers the important return structure and the two operating modes. It leaves branch-resolution behavior and pagination/size limits unaddressed, which are minor for a single-item fetch.

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 80%, so collection, projectId, branch and locale are already documented in-schema. The description adds the meaningful semantic that locale returns translations layered over default values and exposes untranslated fields, but stays silent on branch behavior and identifier sources, so it does not rise above the baseline the schema already sets.

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?

"Reads one item whole" states a specific verb and resource and enumerates the returned facets (slug, status, dates, order, values, file path), which implicitly separates it from list_items and update_item. It never names a sibling explicitly, so an agent must infer the boundary from the singular focus.

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 locale sentence implies usage ('with locale: the item in that language'), giving conditional guidance for one parameter, but there is no statement of when to prefer this over list_items, get_translations, or update_item, and no prerequisites or exclusions.

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