Choisir le magasin

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

The annotations already declare this as a non-readonly, idempotent, non-destructive operation. The description adds useful behavioral context beyond the annotations by explaining that the store choice is remembered for future sessions and depends on the server's Chrome window connection.

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 three tight sentences with no wasted language. The core action is front-loaded, followed by the required id source and the environment constraint.

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 simple two-parameter mutation tool with full schema coverage and annotations, the description covers the essential behavior, persistence, and environment dependency. It could say more about error handling or the optional host workflow, but those gaps are minor because the schema documents the host parameter.

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 coverage is 100%, so the schema already documents both store_id and the optional host parameter thoroughly. The description reinforces that store_id should come from find_stores, but it does not add meaningfully more detail about parameters than the schema provides.

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 states a specific verb and resource: it selects the active store and persists that choice for future sessions. It also ties the tool to find_stores, which helps distinguish it from discovery tools like find_stores and get_store.

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?

It clearly directs the agent to use the id returned by find_stores, establishing the intended workflow. It also adds the important constraint that shopping only works on the drive where the server's Chrome window is connected, though it does not explicitly state when not to use the tool.

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