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

No annotations are provided, so the description bears the full burden. It omits important behaviors such as pagination (limit/offset), default radius, conflict handling when both location types are provided, and the safety/read-only nature of the operation.

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, no wasted words. The purpose is front-loaded, and usage follows concisely. The parentheses for tag examples add value without clutter.

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 main parameter groups but misses pagination (limit/offset) and does not explain default behavior (e.g., radius default 15). An output schema exists, reducing the need for return value description, but gaps remain.

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?

With 0% schema description coverage, the description adds meaning to lat/lng, radius_miles, city, state, tag, and open_now, including example tags. However, it fails to document limit and offset, which are in the schema but lack explanation.

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 finds Indian apparel and jewelry stores, listing specific examples like sarees and lehengas. It distinguishes from siblings like 'get_apparel_details' (for details) and 'search_apparel_by_text' (text search).

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 explains the two location modes (lat/lng vs city/state) and the optional filters (tag, open_now), providing clear context for parameter usage. However, it does not mention alternatives or when not to use this tool.

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