set_location

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

With no annotations, description partially discloses behavior: use before adding items, 'detect' parameter action. Lacks details on side effects, errors, or what happens if used after adding items. Moderate transparency.

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 sentences plus a flow instruction; moderately concise but includes procedural steps that could be streamlined. Front-loads purpose but then dives into sequence.

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 the simple tool with one parameter and output schema, description provides a usage flow and context with siblings. But lacks information on error handling, output, or boundary cases. Sufficient for basic use.

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?

Adds meaning to the single parameter 'location_name' by showing 'detect' as a special value and implying it can be a search query. However, does not specify format or valid alternatives beyond 'detect'. Schema has no description, so partial compensation.

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 tool sets the delivery location via search, and distinguishes from related siblings like get_addresses and select_address by specifying when to use each. It includes a specific example for 'detect'.

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?

Provides an explicit flow with ordered steps (login -> set_location -> add items -> check_cart) and a clear alternative for after adding items. Also states not to use this tool for fixing address after adding items.

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