compare_teams

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

No annotations provided, so description carries the burden. It discloses that output is grouped by position with projected points and totals, which is useful. However, it doesn't mention whether the comparison is limited to starters, how fuzziness works, or what happens if a team name is ambiguous.

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 concise and front-loaded, explaining what it does and then detailing parameters and output format. It could be slightly more efficient, but no significant 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?

With an output schema present, the description needn't explain return values, but it does hint at them. However, given no annotations and low schema description coverage, the description is incomplete regarding behavioral traits and edge cases.

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 0% for descriptions, but the description explains that both parameters accept team name or owner with fuzzy matching. This adds meaning beyond the bare schema, though it could specify the fuzziness behavior more precisely.

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+resource: comparing two teams' starting lineups position by position. This is clearly distinct from siblings like get_team_roster or get_head_to_head, which serve different purposes.

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?

No when-to-use guidance or alternatives mentioned. While the purpose implies comparison of teams, it doesn't explain when to prefer this over get_team_roster called twice or get_head_to_head.

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