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

With no annotations, the description carries the burden well: it discloses provenance (system-generated from catalog + sales), freshness (~monthly refresh), that merchant corrections are applied on top, and that `_merchantCorrected` fields are authoritative. It stops short of stating permissions, behavior when no data exists, or response size limits, so it is strong but not exhaustive.

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?

Front-loaded with the return contract, then provenance, then usage, then the alternative — a sensible order with no filler sentences. The field enumeration and parenthetical for giftLed are dense but each clause earns its place; it could be tightened marginally but nothing is wasted.

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?

There is no output schema and no annotations, so the description must convey the return shape itself — and it does, enumerating the profile fields and flagging `_merchantCorrected` as authoritative. With only two fully documented, optional parameters and usage guidance included, an agent has everything needed to call and interpret this tool.

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 description coverage is 100%, so both `store` and `_offset` are already documented in the schema; the description's 'Omit store to get every store in the workspace' largely restates that. It adds no syntax, format, or edge-case detail for the parameters beyond the schema, so the baseline 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?

States a specific verb and resource ('Return what the system understands about a store's IDENTITY') and enumerates the exact content returned: primaryCategory, priceTier, audience, positioning, giftLed, revenue-weighted category mix, and price range. That content signature makes it distinguishable from siblings like get_store_summary or get_store_notes without opening either schema.

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?

Gives explicit triggers ('use as a session opener to orient yourself before answering', 'when the user asks what do you know about my store?') and names the corrective alternative: 'If the profile is wrong, call update_store_profile.' Both when-to-use and the escalation path are spelled out rather than inferred.

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