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

Annotations already declare readOnlyHint=true and the description is consistent with that ('GET /retailer'). Beyond annotations it discloses the exact payload contents, which is valuable given there is no output schema, and adds operational guidance about the time zone field.

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 tight sentences plus the endpoint line, front-loaded with what the resource is before the workflow tip. No filler or restatement of the name.

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 zero-parameter read with no output schema, the description fully compensates by enumerating every returned field and explaining how to use one of them. An agent has everything needed to call it and interpret the result.

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 the baseline is 4; there is nothing for the description to disambiguate. No parameter-level detail is needed or missing.

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 resource (the connected store/retailer) and enumerates exactly what the response carries: id, name, domain prefix, store URL, country, currency, time zone, tax and loyalty/gift-card settings. The phrase 'the connected store' plus the closing 'GET /retailer' distinguishes it from siblings like get_outlet or list_users.

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?

Explicitly recommends it as a first call and gives a concrete downstream use — 'use the time zone to turn a local day into UTC for sales searches' — which tells the agent when to reach for it. It stops short of naming an alternative tool to avoid, but no true alternative exists for this data.

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