tiffany_stores

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. It explains the ordering behavior ('ordered by distance') and enumerates the returned data fields (address, phone, opening hours, services, specialties, live open/closed status). It stops short of stating that this is a read-only operation, but the verb 'Find' and the non-mutating scope make that reasonably clear.

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 concise and front-loaded, with the core purpose in the first sentence and supporting behavior in the second. There is minor redundancy in repeating 'Find' across both sentences, but no filler or unnecessary detail.

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 read-only lookup tool, the description is reasonably complete: it identifies input location semantics, specifies ordering, and enumerates the output fields, which is especially important because there is no output schema. It does not cover default radius/limit behavior, but those parameters are documented in the schema and are not critical for basic invocation.

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 description coverage is 100%, so the parameters latitude, longitude, limit, and radius are already documented in the schema. The description adds the semantic context that stores are found 'near a coordinate' and 'ordered by distance,' but it does not add new details about parameter formats, defaults, or interactions beyond what 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 names a specific verb and resource: 'Find Tiffany & Co. store locations.' It also narrows the scope to physical stores, boutiques, and cafes near a coordinate, which clearly distinguishes this tool from sibling tools like tiffany_search or tiffany_product. The 'ordered by distance' detail adds further precision.

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 clearly implies when to use this tool: when the agent needs physical Tiffany & Co. locations near a latitude/longitude coordinate. It does not explicitly name alternatives or state when not to use it, but the store-location framing and coordinate requirement give enough context for an agent to route correctly.

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