get_new_arrivals

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, clearly establishing safe read-only behavior. The description adds no further behavioral details, but with annotations present, the bar is lower for additional context. The tool has no side effects, so the annotation coverage is sufficient.

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 sentences, direct, and free of extraneous detail. It states the function and the intended use without redundancy, achieving high clarity in minimal length.

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 provides a complete definition and clear use cases, allowing an agent to decide when to call this tool. Since it is a read-only list with no parameters and the sibling tools are differentiated, no further context is needed.

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 tool has zero parameters, so there is nothing to explain. The schema coverage is 100% (empty object), and the description does not need to add parameter meaning. This dimension is trivially satisfied.

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 lists species detected for the first time ever or newly arrived this season/year, providing a specific verb (list) and resource (species). It distinguishes itself from siblings like get_recent_detections and get_today_summary by focusing on new arrivals rather than all recent activity.

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 gives explicit use cases: 'Use this to spot migration events, rare visitors, or new residents.' This tells the agent when to invoke the tool, though it does not explicitly contrast with sibling tools. However, the purpose clarity already differentiates it from alternatives.

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