get_default_store

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'Show' implies a read operation, but the description does not state whether the operation is safe/non-mutating, whether it requires certain permissions, what happens if no default store is configured, or any side effects. This is minimal behavioral transparency beyond the core purpose.

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, focused sentence with no filler or redundancy. It is appropriately sized for the simplicity of the tool and front-loads the core information ('Show the store currently used').

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?

Given that this is a zero-parameter getter with an output schema present, the description is nearly complete for invoking the tool correctly. It clearly states what the tool returns (the current store) and its scope (prices and availability). It could optionally mention the relationship with set_default_store or behavior when no default exists, but these are not critical for a simple getter.

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 has zero parameters and the schema already covers everything at 100%. With 0 parameters, the baseline is 4. The description adds no parameter-specific details, but there is nothing to describe, so this baseline is appropriate.

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 uses a specific verb ('Show') and a specific resource ('the store currently used for product prices and availability'). This clearly distinguishes it from siblings like set_default_store (which changes the default) and find_stores (which searches stores).

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?

There is no explicit guidance on when to use this tool versus alternatives. The usage is implied by the name and description: call it to retrieve the current default store. However, it does not mention exclusions like 'to change the store, use set_default_store', so the guidance remains implicit rather than explicit.

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