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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the refresh cadence ('Refreshed every morning') and data window ('next 8 days'), which tell the agent how fresh and how far-reaching the data is.

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 the core return content and then the downstream impact. No filler or repetition; efficient for the amount of information conveyed.

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?

No output schema exists, but the description enumerates the key return fields and the derived scoring impact, plus freshness cadence and data window, which is enough for an agent to call it correctly. Minor gap: no guidance on the optional 'week' parameter or default behavior when omitted.

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 50%: 'team' is documented in the schema, but 'week' has no description. 'in a week' and 'next 8 days' give contextual meaning to the week parameter, which compensates somewhat, but the description offers no format or constraint details (e.g., valid week range, whether week is optional).

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?

States a specific resource (weather for each NFL game in a week) and enumerates the returned fields (temperature, wind, gusts, rain chance, roof status) plus derived impact on game total and QB/WR/RB scoring. The sport-specific framing cleanly distinguishes it from sibling invoke_mlb_weather and invoke_pga_weather.

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 scope ('each NFL game in a week', 'next 8 days') implies when the tool is relevant, but there is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives such as the per-sport weather siblings. Usage is inferable but not stated.

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