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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results blend two source types, which is genuine context, but says nothing about result ordering, freshness, or how radius/limit affect behavior.

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 compact sentences with the core purpose front-loaded and examples placed after, which is the right order. The examples are somewhat repetitive (all three express essentially the same 'what's nearby' intent), which trims some value.

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 four-parameter geo-query with no output schema, the description should explain the radius/limit controls and what the returned items look like. It does communicate the content types returned, but leaves the spatial scoping parameters entirely unexplained.

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% across four parameters, and the description only vaguely implies a location via 'near a location'. limit and radius_miles are never mentioned, nor are expected formats or units for lat/lng, leaving the agent to guess from bare type declarations.

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-resource combination (see what's going on near a location) and clarifies it aggregates two content types, shop posts and open houses, together. That implicitly differentiates it from find_nearby_shops and find_open_houses, but the relationship to whats_live_nearby is never addressed.

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?

Three example user utterances ('anything to do near me?', 'what's going on around here?', 'what should I do nearby today?') give useful intent-matching cues for when to call it. However, there is no explicit guidance on when to prefer find_nearby_shops, find_open_houses, or whats_live_nearby instead, nor any prerequisites or exclusions.

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