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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no return format, no pagination, no location or personalization scoping, no indication of whether results are static or user-specific. Three words cannot cover a behavior profile for a list tool with none of the structured hints that annotations would supply.

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 fragment is short but this is under-specification rather than conciseness; there is no front-loaded statement of purpose, scope, or output. Length is not the issue so much as the absence of any earnable content.

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?

With zero annotations, no output schema, and a vague name-synonym description, an agent has almost nothing to decide whether or how to call this versus get_locals_favorites or get_places. The definition is not complete enough to support correct selection or 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 reported at 100% for the single limit parameter, so the schema nominally carries the parameter documentation and the baseline is 3. The description adds nothing about what limit controls or its default/max, but the rule sets the baseline here regardless.

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?

"Curated local gems" is a noun phrase that essentially restates the tool name get_local_gems rather than stating a verb and resource. An agent cannot tell what a "gem" is (a place? a venue? a saved item?) or how this differs from sibling tools like get_locals_favorites, get_places, or get_top_restaurants.

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?

There is no guidance on when to use this tool, when not to, or which of the 30+ sibling discovery tools it supersedes or complements. The agent is left to guess entirely from the name.

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