migration_forecast

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

With no annotations, description carries full burden. Discloses data types (traffic, species, totals, summary) and seasonal availability. Missing details on authentication, rate limits, or return format, but adequate for a read-only forecast.

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?

Two sentences, front-loaded with purpose and data types, followed by a necessary constraint. No wasted words.

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, description adequately explains return value (traffic, species, totals, summary). Also covers availability window. No missing elements for a simple tool.

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 has 100% description coverage. Description adds value by specifying defaults (region code defaulting to Hamilton County, OH, date defaulting to today) and providing example format for region_code.

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?

Clearly states the tool gets BirdCast migration data for a region and lists specific data types (last night's traffic, expected species, seasonal totals, summary). Differentiates from siblings like birding_weather or species_finder.

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?

Explicitly states availability only during migration seasons (Mar-Jun, Aug-Nov), guiding when to use the tool. Does not name specific alternatives for off-season, but context signals provide sibling tools.

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