afl_compseasons_list

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

The description discloses the return format including pagination structure and key fields. With no annotations, it clearly implies a read-only operation by listing data, and provides a concrete output schema.

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 with two sentences covering purpose and return format. It is front-loaded with the primary action, though it sacrifices parameter explanation.

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 description provides a partial return structure and date range, but lacks details on authentication, rate limits, or complete parameter semantics. For a simple list tool, it is adequate but has gaps.

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% and the description does not explain the meaning of the 'page' and 'pageSize' parameters. The parameter names are self-explanatory but the description adds no additional context beyond the schema names.

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 lists comp seasons across all competitions with a specific date range (2012–present). It differentiates from siblings like 'afl_competition_compseasons' by explicitly mentioning 'across all competitions'.

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 explicit guidance on when to use this tool versus alternatives like 'afl_competition_compseasons' for a specific competition. The description only states its scope without discussing exclusions or alternatives.

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