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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the useful fact that it returns both a postponed-games list and risk-alert records with a percent and detail field, which partially compensates for the missing output schema, but it says nothing about auth needs, freshness/latency, or whether results are team-scoped when the parameter is omitted.

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, no filler, and the payload contents are front-loaded before the call-to-action. Slightly tight to the point of leaving the omitted-parameter behavior unstated, but nothing is wasted.

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, single-optional-parameter lookup with no output schema, the description covers what the tool returns and when to reach for it. The remaining gap is behavioral edge cases (empty team parameter, data staleness) rather than anything that would cause a mis-invocation.

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 description coverage is 100% for the single optional team parameter, so the schema already carries the parameter meaning. The description adds no filtering semantics of its own, not even what an omitted team returns (all games vs. none), which is the one ambiguity the schema leaves open.

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 (games postponed today) plus a second output class (active postponement risk alerts with weather risk percent and detail), so the agent knows this is not a generic weather tool. It never names the sibling it differs from (e.g. invoke_mlb_weather), so sibling disambiguation is left to inference.

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?

"Check this before you stack a team" gives a concrete moment to use the tool, which is more than nothing. But there is no when-not guidance and no alternative tool is named for the overlapping weather/forecast case, so usage is only implied rather than routed.

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