afl_competition_compseasons

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

No annotations are provided, so the description must carry full behavioral disclosure. It only states that the tool lists comp seasons and gives a brief return format hint ({meta, compSeasons:[...]}). It does not mention pagination, authorization, rate limits, ordering, or error behavior. The minimal description leaves significant uncertainty for an agent.

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 very concise (two sentences), but it is under-specified. It could be improved without adding significant length by including parameter descriptions and usage context. The structure is straightforward.

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 the tool's simplicity (2 params, no output schema) and lack of annotations, the description is incomplete. It fails to explain parameters, usage, or behavioral details. An agent would need additional context to use this tool correctly.

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?

Input schema has 0% description coverage; the description does not describe any parameter. The agent must infer the meaning of competitionId and pageSize solely from their names. This is insufficient for correct invocation, especially since pageSize has a default value and its behavior (e.g., max value, pagination) is not explained.

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 within one competition, specifying the verb (List) and resource (comp seasons) and scope (within one competition). This distinguishes it from siblings like afl_competition_get (gets a competition) and afl_compseason_get (gets a single comp season). However, it does not explicitly differentiate from afl_compseasons_list, which likely lists all comp seasons without competition filter.

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 guidance on when to use this tool vs alternatives. There is no mention of prerequisites, context, or scenarios where this tool is appropriate. The description lacks any 'when to use' or 'when not to use' information.

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