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

Beyond the read-only annotations, the description discloses important behavioral limits: unprovable rounds are marked missing with a reason and no ties, pairings are never guessed, and placeholders are only added where the draw tree is proven. This is exactly the kind of integrity and edge-case context an agent needs.

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 what the bracket contains, then proceeds through sport-specific usage and data-provenance rules. It is dense but every clause is relevant; better formatting could improve scanability, but it is not padded.

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 the return value and does so thoroughly: it describes rounds, ties, legs, aggregates, advancement methods, and provenance. It also explains missing-data behavior, leaving little an agent needs to infer.

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 four parameters. The description reinforces the sport-specific mappings and defaults but adds little beyond the schema, making the baseline 3 appropriate.

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 establishes that this tool returns a knock-out bracket, detailing rounds, ties, legs, aggregate, advancement, and sourcing. It is a precise resource description, but it does not explicitly contrast with sibling tools, which keeps it from a 5.

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 specifies the contexts in which the tool applies: soccer cups and European knock-out phases, tennis draws, and snooker/darts tournaments. It does not name alternative tools or state exclusions, but the sport-by-sport guidance is clear enough for selection.

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