set_store

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

The description discloses that the selection is 'persisted for future calls,' which is key behavioral information. However, it does not mention whether login is required, if the previous selection is overwritten, or any side effects. With no annotations, the description carries full burden and could be more transparent.

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 consists of three concise sentences: purpose, persistence, and prerequisite. Every sentence adds value with no fluff. Front-loaded with the primary action.

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 description covers the tool's purpose, persistence, and a prerequisite. For a simple tool with two parameters and no output schema, it is mostly complete. However, it does not describe the return value or error cases, which could be helpful for an agent.

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 description adds limited value beyond the schema. It restates the storeId source and adds context about per-store pricing, but does not elaborate on the provider parameter's default or meaning. The description adequately complements the schema without major 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 clearly states the verb 'Select' and the resource 'active store' for providers with per-store pricing. It distinguishes from sibling tools like browsing or cart operations, though it does not explicitly state what it does not do.

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 provides clear context ('for a provider with per-store pricing') and directs users to get store IDs from list_stores, a sibling tool. It does not explicitly mention when not to use this tool, but the context is sufficient for most uses.

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