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

Beyond the annotations, which already declare this a safe read-only/idempotent operation, the description discloses that ranks apply the real NFL tiebreaking procedure, reports which step decided each rank, is computed from final scores, defaults to the current season, and costs 2 credits. These are valuable behavioral details an agent 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?

The description is front-loaded with 'Use for' and packs the scope, output fields, tiebreaking behavior, data source, default, and cost into a few dense sentences. Every sentence contributes useful information without waste.

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?

The tool has an output schema, so return values need not be explained, and the annotations cover safety. The description sufficiently completes the picture with scope, computation method, tiebreaking transparency, default behavior, and credit cost.

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?

With 100% schema description coverage for all three parameters, the schema already documents season, division, and conference. The description only repeats that it defaults to the current season, so it adds little beyond the structured parameter definitions; baseline 3 is appropriate.

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 explicitly states the tool is for regular-season standings and playoff seeding, and enumerates the specific outputs: record, win%, points for/against, various splits, streak, division rank, and conference seed. This clearly distinguishes it from sibling stat tools such as get_team_stats or get_advanced_stats.

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 gives clear usage context with 'Use for regular-season standings and playoff seeding' and notes it defaults to the current season. It does not explicitly name when not to use it or point to alternatives, but the intended use case is unambiguous.

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