list_teams

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

With no annotations provided, the description carries the behavioral burden. It clearly conveys a read-only listing operation over all Division 4 teams and specifies the returned attributes. It does not discuss ordering, pagination, or data freshness, but for a zero-parameter list tool these omissions are minor.

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 a single, front-loaded sentence with no filler. Every phrase contributes: the action, the scope, and the returned fields.

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?

For a simple zero-parameter tool with no output schema, the description is nearly complete: it states the scope and the returned fields. It could add one note about using this as a team-ID source or how it differs from standings, but nothing essential is missing for invoking the tool.

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 tool has zero parameters, so the baseline is 4. The description reinforces that the tool returns all teams with no filtering, which is the only parameter-related information an agent needs.

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 uses a specific verb ('List') and a clear resource ('all Division 4 teams'), and names the returned fields (group, record, id). It is immediately clear what the tool does and it is distinguishable from the more specialized sibling tools like roster, standings, and team_batting.

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 usage context is somewhat implied: an agent can infer it is the team-enumeration tool for getting team IDs and basic records before diving into specialized views. However, it does not explicitly state when to use this tool instead of alternatives such as standings or roster, nor does it mention any exclusions or prerequisites.

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