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

Beyond the read-only and idempotent annotations, the description discloses critical behavior: predictions are released only after entries close, before which released is false, expertPick and expert are null, and expertSample is 0. It also defines the expert cohort qualification and the minimum 20-player threshold for shares.

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 dense but front-loaded, beginning with the core resource before moving to cohort definition, release timing, and null behavior. Most clauses earn their place, though the single paragraph could be slightly easier to scan.

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?

With no output schema, the description carries the burden of explaining returns and does so for key fields such as expertPick, expert, expertSample, released, and the home/draw/away splits. It is nearly complete for a one-parameter read tool, though the full response structure is not exhaustively described.

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 100%, so the enum values are already documented. The description still adds useful meaning by expanding btm as Bundesliga TipMaster and tmi as TipMaster International, going beyond the bare enum labels.

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 specific resource and scope: the current TipMaster Classic round, with 25 matches per game, expert cohort splits, majority picks, and crowd splits. It also distinguishes the expert cohort from the whole crowd, which differentiates it from a generic consensus tool like get_consensus.

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 description implies when the data is usable by explaining the Friday 18:00 Europe/Berlin publication time and the pre-release null state. However, it does not explicitly say when to choose this tool over siblings such as get_consensus or get_match_prediction.

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