Set Market

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the selection is a persistent default affecting search and basket, but says nothing about session scoping, what happens to an existing basket, or what occurs if the identifier is invalid or ambiguous.

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 tight sentences with the purpose front-loaded and the accepted input forms second; nothing is wasted. It could still be marginally tighter given how little it covers.

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?

An output schema exists, so return values need not be explained. For a single-parameter mutation with no annotations, however, the description should say more about persistence, error behavior, and prerequisite lookup tools to be fully actionable.

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 0% – the single 'market' string parameter is completely undocumented in the schema. The description compensates partially by stating that an id, name, or city is accepted, which is real value beyond the schema, but gives no format examples or disambiguation rules for the three accepted forms.

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?

States a specific verb and resource ('Select the market') and clarifies the effect: it becomes the default for search and basket. That is enough to distinguish it from a lookup tool like find_markets, though no sibling is named 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?

The description never says when to reach for this tool versus find_markets or market_info, nor does it state prerequisites such as resolving a market first. The intended use is only implied by the word 'default'.

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