email_report

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

The description explains billing impacts (1 credit for summary, 1 credit/property with limit), recipient restriction, and that limit includes top N properties. Annotations provide no behavioral details, so description adds significant value. No contradiction.

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, front-loading the core action and key constraints. It is concise, though could be slightly more structured to highlight parameter groupings.

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 10 parameters and no output schema, the description leaves most filter parameters unexplained and does not mention success/error outcomes. It provides sufficient context for the core function but is incomplete for full 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 coverage is only 20% (storm_id and limit have descriptions). The description explains limit's effect but not the other 8 parameters (value_max, value_min, etc.), which likely filter properties. The description fails to compensate for missing schema descriptions.

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 emails a swath report summary to your account email, listing what the summary includes (max hail/wind, swath area, etc.). It distinguishes from siblings like find_storms and show_swath_map by focusing on email delivery.

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?

Provides detailed usage context: it emails only to the account email, explains billing for summary vs. including properties with limit, and references similar tools. However, it does not explicitly state when not to use this tool or suggest alternatives for viewing without emailing.

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