Region bundle: air + rain + river ($0.10)

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

With no annotations provided, the description carries the full burden. It mentions the cost ($0.10 USDC) and the output (air, rain, river, narrative) but does not disclose other behavioral traits like rate limits, idempotency, or whether the call is destructive. The absence of such details leaves gaps for a tool with significant implications.

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 concise sentences. The first sentence clearly states the bundle composition and narrative, and the second provides cost and location guidance. Every word is relevant, and the structure is efficient for quick comprehension.

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 the tool has a single parameter and no output schema, the description adequately explains what the tool returns (air, rain, river, narrative) and mentions cost and region format. It references gauge_preview for region lookup, which is helpful. Minor missing details about output format or data units, but overall sufficient for a low-complexity 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?

The schema already describes the 'loc' parameter with an example. The description adds a second example ('us-chicago') and references gauge_preview for valid regions, which is moderately helpful. However, since schema coverage is 100%, the description does not dramatically increase semantic understanding beyond what the schema provides.

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 that this tool provides a bundle combining air quality, precipitation, and nearby river data for a US city, along with a narrative. It identifies the resource and its components, though it does not explicitly differentiate from sibling tools like gauge_river_free or gauge_preview.

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 implies when to use (for a three-leg bundle) and suggests checking gauge_preview for valid region identifiers. However, it lacks explicit guidance on when not to use this tool or how it compares to alternatives such as gauge_crop_drought or gauge_flood_risk.

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