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

With no annotations and no additional behavior details, the description does not disclose how proximity is determined, coordinate system, sort order, error behavior, or consequences of the language/audio parameters.

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 a single, direct sentence with no filler words, making it highly concise and front-loaded.

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 lacks essential context such as search radius, result limits, default language/audio behavior, and expected output structure, making it incomplete for a tool with five parameters and no output schema.

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?

The schema has no parameter descriptions, and the description only hints at lat/lon via 'coordinate'. It does not explain lang, audio, or limit semantics, despite these parameters being present.

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 action ('Return'), the resource ('nearby public heritage places'), and the input ('a coordinate'), making it distinct from sibling tools like search_places or get_place.

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 implies coordinate-based proximity search but does not explicitly state when to prefer this tool over alternatives such as search_places or get_place, nor does it mention exclusions.

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