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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds substantial behavior beyond that: live vs cached counting, per-sheet failure isolation (a failing count falls back to stored item_count while other sheets still return), Shopify sheets retaining stored counts, and count drift between list_items pages. It stops short of describing ordering, scope of sheets returned, or the general shape of sheet objects.

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 purpose is front-loaded in one short clause, but the body is a dense, repetitive block about item_count: the live-count idea is restated across four sentences, and the list_items totalItems comparison appears twice. The detail earns its place, but the ratio of count nuance to core listing behavior is skewed.

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 parameters and no output schema, the description must carry return-value semantics, and it does so thoroughly for item_count. It leaves other essentials unstated: what other fields a sheet entry carries, whether archived or catalog sheets are included, ordering, and how this relates to list_catalog_sheets.

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 tool takes zero parameters, so there is nothing for the description to disambiguate at the input level. Baseline 4 applies; the surrounding text concerns return values rather than inputs.

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 first sentence states a specific verb and resource: 'List sheets for this organization,' with an explicit organizational scope. It does not, however, distinguish itself from nearby siblings such as list_catalog_sheets, list_sheet_templates, or get_sheet_settings, so an agent still has to infer which listing tool applies.

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 explains output semantics of item_count but gives no when-to-use guidance, no prerequisites, and no exclusions relative to sibling tools. An agent learns more about how counts behave than about when this tool should be selected over alternatives.

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