get_results_by_opponent_tier

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds meaningful behavior: tiers come from live league standings, top/bottom tier_size are defined, and it clarifies the 'middle' as everyone in between. No contradictions with annotations; it could add more detail on output, but the output schema covers that.

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 a crisp one-sentence purpose, followed by a short explanatory paragraph and a well-organized Args block. Every sentence adds value, and there is no redundant or filler content.

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 read-only annotations, an output schema present, and thorough parameter explanations, the description fully equips an agent to select and invoke the tool. It explains tier derivation, provides an example use case, and defines constraints, making it self-sufficient.

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?

The schema has zero parameter descriptions, but the description's Args section fully compensates by explaining team_id as an ESPN numeric team ID and tier_size with its default, minimum, and constraint that 2*tier_size must not exceed league size. This goes well beyond the schema's type/default fields.

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 tool gets a team's W-L-T splits against top-tier, middle, and bottom-tier teams, using a specific verb and resource. It distinguishes itself from sibling tools like get_standings or get_team_schedule by its analytic angle, but it doesn't explicitly name an alternative tool or contrast with them.

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 provides clear context for when to use the tool—e.g., asking 'how does this team do against the top of the table?' and avoiding manual result scanning. It also explains how tiers are derived. However, it doesn't explicitly state when-not-to-use or name a sibling tool as an alternative, so it stops short of a 5.

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