get_hotspots_in_region

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic get action and a use case, omitting details such as what data is returned, whether it is read-only, any rate limits, or prerequisites beyond the schema. This is insufficient for an agent to understand the tool's full 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?

The description is one sentence, front-loaded with the core action, and the trailing use-case phrase adds value without redundancy. Every word earns its place.

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?

Given the tool's simplicity (2 params, 1 required) and no output schema, the description provides purpose and usage context, but lacks behavioral details like response format, sorting, or how it relates to other hotspot tools. It is minimally viable but not complete for an agent that needs to anticipate return values or limitations.

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?

Both parameters are fully documented in the schema, so the baseline is 3. The description adds no additional meaning beyond the schema, such as clarifying the expected format of regionCode or the effect of the 'back' parameter.

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 it 'Get birding hotspots in a region', specifying the verb, resource, and scope. This distinguishes it from sibling tools like get_nearby_hotspots (coordinate-based) and get_hotspot_info (details for a specific hotspot). The 'great for trip planning' reinforces the intended purpose.

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 phrase 'great for trip planning' provides a clear context for when to use this tool, but it does not explicitly mention alternatives or when not to use it (e.g., when working with coordinates rather than a region code). This is clear context without exclusions.

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