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

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description need not cover that. It adds the meaningful behavioral trait that results are time-sensitive 'right now' postings, but says nothing about volume, pagination behavior, or how limit/radius affect results.

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 with the purpose front-loaded, followed by illustrative example queries. It is tight with no padding, though the example phrasings are somewhat redundant with one another.

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?

There is no output schema and no annotation describing return values, yet the description never explains what a result contains (shops, posts, deals, timestamps?). Combined with zero-coverage parameters and no return-format guidance, an agent cannot predict the response shape or the effect of limit/radius_miles.

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 0% and none of the four parameters (lat, lng, limit, radius_miles) have descriptions, so the description carries the full burden. It only loosely implies a location ('near a location'), giving no meaning to lat/lng format, the units of radius_miles, or the default/range of limit.

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: 'See what shops are posting right now near a location,' which conveys a real-time feed of nearby shop posts. It is clearer than the generic siblings (find_nearby_shops, whats_happening) because of the 'live/right now' framing, but it never explicitly contrasts itself with find_nearby_shops, which overlaps heavily.

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 example queries ('what's live near me?', 'any deals nearby right now?') imply the conversational intent this tool serves, which is useful context. However, there is no explicit when-to-use versus when-not guidance, and no mention of the closely related find_nearby_shops sibling, leaving the routing decision to inference.

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