current_store

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds the useful fact that prices and balances depend on the current store, but it does not disclose side effects, read-only status, or what the tool actually does when invoked. It reads more like a definition than a behavioral specification.

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 description is a single short sentence with no filler or redundant content. Every word contributes meaning about the store's role and its impact on prices and stock, so it earns full marks for conciseness.

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?

The tool is simple with no parameters, so calling it is trivial, but the description does not explain what the agent will receive in return or how the output is structured. It provides enough context for selection when the current session store is needed, but without an output schema or return-value description, the definition is incomplete for full end-to-end usage.

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 input schema has zero parameters, so there is nothing to document. Per the rubric, a zero-parameter tool receives a baseline score of 4, and the description does not need to compensate for any parameter gaps.

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 identifies a specific resource (the store attached to the current session) and notes that prices and balances depend on it, but it is phrased as a noun phrase rather than an action like 'returns' or 'gets.' This leaves some ambiguity about whether the tool returns the store or simply represents it, and it does not explicitly differentiate it from siblings like store_details.

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 gives no guidance on when to use this tool versus alternatives such as store_details or set_region. It does not state 'use this to get the current store' or mention any exclusions, so the agent must infer usage from the name and context.

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