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 valuable return-content context (what data categories come back), which matters since there is no output schema, but it says nothing about pagination, data freshness, or auth needs.

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?

Purpose and scope are front-loaded in the first sentence, followed by the two invocation modes. The data enumeration is a bit list-heavy but each item conveys the breadth of the breakdown, and there is no redundant filler.

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?

With no output schema, the description correctly carries the burden of describing returned content and both input modes. It is nearly complete for a read-only aggregation tool, though it leaves an agent unsure how it relates to the narrower sibling tools covering the same categories.

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% — the 'game' param has no schema description at all. The description compensates by specifying the format ('PHI@CHI') for game and clarifying that 'team' accepts a single team, which the schema's 'KC or PHI' example reinforces. This meaningfully fills the coverage gap.

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 verb and resource: 'One NFL game breakdown from the BankrollSZN Matchups page', then enumerates the bundled data (lines, Monte Carlo picks, Elo, DVP, coverage, personnel, injuries). This is clear, but it does not distinguish itself from sibling sub-tools like invoke_nfl_line_matchups, invoke_nfl_elo, or invoke_nfl_dvp whose content appears folded into this one.

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?

It says how to invoke ('Pass a game like PHI@CHI or one team') and what happens with no arguments ('lists this week's games'), which is useful implied usage. But it gives no when-to-use guidance relative to alternatives — an agent cannot tell whether to call this versus the single-purpose NFL tools it aggregates.

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