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

With no annotations, the description must carry behavioral weight, and it does disclose meaningful context: schedule rules (Saturday 17:00 UTC, last Sunday finals), eligibility (open to all vs weekly winners qualify), and the fact that running and recent events are included alongside upcoming ones. It stops short of stating ordering, result limits, or pagination, which matters for an accumulating event list.

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?

A single sentence that front-loads the resource and packs schedule, eligibility, and payload into two compact parentheticals. Dense but every clause adds information; a slightly clearer lead-in verb would improve scanability.

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 parameterless read tool with no output schema, the description covers content, cadence, eligibility, and time scope. Only ranking/ordering and volume of returned events are missing, which is a minor gap.

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?

Zero input parameters, so there is nothing for the description to disambiguate and the baseline applies. The space is instead used to explain what the tool returns.

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 names the resource precisely (chess tournaments) and the exact set returned: next weekly, next monthly finals, plus running and recent events, with start times and entrant counts. It distinguishes itself from tournament_get/join/leave by framing the tool as a discovery/listing surface, though it never states the verb 'list' outright.

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?

Usage is implied rather than stated: an agent can infer you call this to discover tournaments and then use tournament_get for one, or tournament_join to enter. There is no explicit when-to-use/when-not or named-alternative routing.

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