ht_rx_session

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries real weight here and delivers: it explains that pharmacy access needs a separate sign-in at harristeeter.com/rx, that an unknown browser requires a one-time code, and that the session expires after one hour and cannot be extended. That is meaningful context an agent could not derive from the annotations, though it stops short of saying what the tool returns or how an inactive result should be handled.

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, zero filler, and the core check is front-loaded before the supporting session-lifecycle detail. Every clause (separate sign-in, one-time code, one-hour limit, non-extendable) conveys distinct operational information.

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, so the description should indicate what an 'active' or 'inactive' result looks like and what the agent should do next. Those gaps are modest given the tool's low complexity and zero parameters, but they leave the definition short of fully self-contained.

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?

There are zero input parameters, and the schema is empty, so there is no parameter semantics to add. The baseline for a parameterless tool applies; the description correctly avoids inventing 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 description opens with a specific verb and resource: 'Check whether the Harris Teeter pharmacy session is active.' That distinguishes it clearly from the prescription- and refill-oriented ht_rx_* siblings, though it never names those siblings or states a relationship to them explicitly.

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 check should precede other pharmacy calls, but the description never says when to call it, what to do if the session is inactive, or how to trigger the sign-in it describes. The one-hour lifetime hints at why timing matters, but the routing guidance stays implicit.

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