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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavioral context beyond annotations: rankings are bounded to roughly the top 200 entries, pagination uses limit and offset, and 'final' marks the last page. It does not discuss auth or rate limits, but those are less critical for a safe read tool.

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 front-loaded with the core purpose, then filters, pagination behavior, and the sibling alternative. Despite covering ten ranking types, it stays compact and every sentence contributes useful information.

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 rich schema and the presence of an output schema, the description is complete enough: it explains what the tool returns, how to filter and page, the ranking cap, and when to prefer a sibling. No important calling information is missing.

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 schema already documents all six parameters in detail. The description still adds meaningful semantics beyond the schema by noting that a ranking is capped around 200 entries and that 'final' indicates the last page, which helps interpret limit and offset even though the schema allows offsets up to 1000.

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 verb and resource: it returns a page of one of the ten Top-Amateurstatistiken rankings, with concrete categories such as top teams by goals, goal ratio, highest-scoring matches, and top scorers. It also distinguishes the tool from fussballde_top_scorers, so an agent can tell which stats-ranking tool to call.

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?

It explicitly routes one use case to a sibling: 'Use fussballde_top_scorers for one competition's scorers.' That gives clear alternative guidance, but it does not address other nearby options such as national top scorers or explicitly state when not to use this tool.

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