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

Annotations already mark it as read-only and open-world, and the description adds meaningful behavioral context beyond that: quota consumption, agriculture API access requirement, and the end-date-exclusive date range. It does not cover return format or rate-limit specifics, but the added constraints are substantial.

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 tight sentences front-load the operation, limits, and prerequisites with no wasted words. The most important constraints appear immediately.

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?

For a read-only historical weather retrieval tool with no output schema, the description covers scope, date-range limits, quota, and access prerequisites. It does not describe the returned fields, but the core invocation constraints are adequately covered.

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 high at 83%, so the schema already explains most parameters. The description still adds value by clarifying the hourly maximum of 7 days (not present in the schema) and reinforcing the 31-day limit and exclusive end date.

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 states a specific verb and resource: read agriculture weather history, with daily or hourly granularity. It is clear what the tool does, but it does not explicitly distinguish the resource from siblings like weatherbit_daily_history or weatherbit_energy_history.

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 useful usage conditions: historical API quota is consumed and agriculture API access is required. However, it does not say when to choose this tool over sibling history tools or when not to use it.

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