list_teams

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

With no annotations, the description carries full burden. It discloses filter and pagination behavior but does not explicitly state that the tool is read-only, or mention rate limits, response size caps, or authentication requirements. Some traits are implied but not stated.

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, each packed with information. No redundant words. Front-loaded with purpose and key features.

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?

Given no output schema, the description explains the output (team UUIDs) and how to use them. It covers filtering and pagination. However, it does not describe the full response structure (e.g., fields like team name, logo), which might be inferred from usage with other tools. Overall, sufficient for an agent.

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%, so parameters are well-documented in the schema. The description adds 'Filter by league' and 'Paginate with cursor' but does not provide additional meaning beyond what is already in the schema descriptions.

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 it lists teams, emphasizes it's a reference resource, and explains its purpose in relation to other tools (list_events, get_team_odds, get_team_stats). It distinguishes from siblings by specifying the output (team UUIDs) and filtering capability.

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?

Explicitly mentions filtering by league and pagination with cursor. Provides usage context (returns UUIDs for other tools). Does not explicitly state when not to use or list alternatives, but the sibling tools list provides context.

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