list_competition_files

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

With no annotations, the description carries the full behavioral burden, but it only says 'List,' which implies read-only access. It does not disclose whether the result is paginated, what fields are returned, whether it lists only metadata, or any authorization requirements.

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 brief with no filler, which is good for conciseness. However, it is under-specified: the single phrase does not carry enough information on its own, so the brevity is closer to minimalism than to well-structured completeness.

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?

There is no output schema, no annotations, and empty parameter descriptions, so the prose description must supply the invocation contract, but it does not. An agent would not know the return format, pagination behavior, or what values `comp` accepts.

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 0% and the description does not explain the `comp` or `page_size` parameters. The word 'competition' weakly hints that `comp` identifies a competition, but there is not enough information for an agent to know how to construct these parameters correctly.

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 states a clear verb and resource: 'List competition data files.' It is understandable and implies a distinction from sibling tools like `download_competition_data` and `list_competition_pages`, but it does not explicitly call out that distinction.

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?

There is no guidance on when to use this tool rather than `download_competition_data`, `list_competition_submissions`, or other related tools. No prerequisites, context, or exclusions are provided, so an agent must infer the appropriate use case from the name alone.

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