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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, so the safety profile is settled. The description adds genuine behavioral context beyond that: it is cross-league, organizer-scoped only, each item is tagged with its league and links to the relevant page, and it explicitly performs no mutation. It does not discuss pagination or result size, which is the only remaining gap.

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?

Front-loaded with the core claim, then the item enumeration, then scope exclusions and the routing sentence. The long item list is dense but each entry adds discriminating detail; the weak spot is that the enumeration could be tightened slightly without losing meaning.

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?

An output schema exists, so return values need not be spelled out, and the description still previews what each item contains (league tag plus link). For a no-arg, read-only aggregator this covers everything an agent needs to select and invoke it correctly, including the sibling it should call afterwards.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline is 4. The description correctly conveys that the call needs no input ('in one call') and does not waste space restating a schema that is empty.

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?

States a specific verb+resource+scope: everything waiting on the person, across every league they run, with an explicit enumeration of item types (unscored matches, unconfirmed reports, disputes, unsent lineups, unpaid members, closing registration, missing settings). An agent can distinguish this aggregate 'inbox' tool from beleeg_prepare_change, beleeg_look_up and the other siblings without opening a schema.

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?

Gives concrete triggering questions ('what needs me this week?', 'am I behind on anything?'), states an explicit exclusion ('Leagues the person only plays in are left out'), and routes to the alternative: 'Nothing here is a change; use it to decide which change to prepare next.' When-to-use, when-not, and the follow-up tool are all present.

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