get_life_list_gaps_at_hotspot

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to mention that results depend on recent observations within the 'back' time window, which is a critical behavioral constraint. It also does not explicitly state that this is a safe, read-only operation.

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, front-loaded sentence that conveys the core purpose without wasted words. It is concise and immediately understandable.

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 no output schema and no annotations, the description plus schema is incomplete. It fails to disclose that the 'back' parameter limits results to a recent observation window, which could lead an agent to expect all-time species records at the hotspot. This missing information is essential for correct usage.

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 100%, so the baseline is 3. The description does not add value beyond the schema's parameter descriptions; it only implies 'locId' via 'specific hotspot' and otherwise adds no additional parameter meaning.

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 uses a specific verb 'Find' with a clear resource ('species at a specific hotspot') and a distinct criterion ('NOT on your life list'). This unambiguously distinguishes it from siblings like get_life_list_gaps_nearby and get_recent_observations.

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 clearly states the intended context: discovering species missing from one's life list at a particular hotspot. However, it does not provide explicit exclusions or name alternative tools for comparison, so it lacks the 'when-not-to-use' guidance.

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