ht_get_store

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine value beyond that by explaining that the value governs both storefront flows (cart, pickup, checkout) and price search, and by promising provenance ('where that choice came from'), which tells the agent to expect an origin field rather than a bare store identifier.

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 front-loaded sentence that states what is returned before qualifying it with the two consumption contexts. No filler, no restatement of the title, and no waste despite the density of the clause structure.

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-only tool with no output schema, the description is nearly sufficient: it says what is reported (the active store and the source of that choice) and why it matters. The one gap is behavior when no store has been selected yet (default/fallback), which an agent might need to interpret an empty or default response.

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 no parameter semantics to document and the baseline of 4 applies. The description correctly spends no space on argument syntax and instead characterizes the result.

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 description names a specific verb and resource: 'Show which Harris Teeter store is in use', and distinguishes two facets (the storefront-selected store used for cart/pickup/checkout vs. the store used for price search). It is clearly a read of current state rather than a search or set operation, though it does not explicitly name ht_set_store or ht_find_stores as the contrasting siblings.

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 only implied: an agent can infer this is the read-side counterpart to setting a store, and the mention of cart/pickup/checkout hints at when the value matters. There is no explicit when-to-use/when-not statement and no routing to ht_find_stores or ht_set_store for the adjacent tasks.

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