get_life_list_gaps_nearby

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does mention the prerequisite of having a life list imported, which is useful, but it does not discuss return format, error handling, or any limitations. This adds some value but lacks depth.

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 two short, engaging sentences with no fluff. It front-loads the core purpose immediately and adds the prerequisite in a clear, separate sentence. 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?

The tool has 5 parameters and no output schema, so the description must compensate. It covers the core behavior and prerequisite, but does not explain what the response looks like or how optional parameters like 'back' or 'native_only' affect results. Given the schema covers parameters, this is adequate but not fully complete.

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 each parameter is already documented. The description does not add any parameter-specific meaning beyond the schema, but it does not need to. The baseline of 3 applies given the schema's completeness.

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 tool's function: 'Find birds near you that you've NEVER seen' — a specific verb and resource that directly conveys the purpose. It differentiates from siblings like get_nearby_observations (all sightings) and get_life_list_gaps_at_hotspot (hotspot-specific) by emphasizing the 'near you' and 'never seen' aspects.

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 provides a clear usage context (finding potential lifers near a location) and includes an important prerequisite ('Requires life list to be imported first'). However, it does not explicitly mention alternatives or when not to use this tool, so it falls short of full guidelines.

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