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

With no annotations, the description covers behavior: it returns scenario breakdown, file count, price, and a purchase link. It clearly states it's free, requires no auth, and creates no order, addressing safety and side effects. No mention of rate limits or other constraints, but sufficient for a preview tool.

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?

Three sentences with no wasted words. First sentence defines purpose and context, second details the return, third lists bundles and safety. Front-loaded with the most important information.

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, the description adequately explains the return structure. It covers required behavior and safety. Could mention related tools or follow-up steps (e.g., use purchase link to buy), but overall complete for a simple preview 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 coverage is 100%, so baseline is 3. The description adds value by listing bundle names with scenario counts (Carbon=10, Titanium=30, Damascus=64) and explaining that optional lat/lon/location provide a location-specific summary. This goes beyond the schema's simple 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 the verb 'Preview', the resource 'fixed-price Forge bundle', and the context 'for a location'. It explains it's a no-account way to buy weather files, which distinguishes it from sibling tools (analyze_weather, chart_weather, etc.) that deal with analysis, not purchasing.

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 (preview before buying) and states it creates no order, but it doesn't explicitly mention alternatives or when not to use. It clearly sets context for a unique tool among siblings.

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