get_all_leagues_summary

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's safe. The description adds the notion of 'separate private contexts' which hints at scoping, but doesn't elaborate on behavior like whether it initializes contexts or just reads them. It doesn't contradict annotations.

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 a single well-structured sentence that leads with the verb and resource. It is concise and complete for its length.

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 tool has no output schema and annotations only cover safety, the description should explain what 'contexts' means, how 'week' affects results, and how this relates to other league tools. The current description is minimal and would benefit from more detail, but it does cover the core action.

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 schema has only one optional parameter 'week' with a default of null, and the description does not explain what 'week' does or how it affects the results. With 0% schema coverage, the description should compensate but doesn't. I'll give a 3 because the parameter is optional and its purpose is somewhat inferable.

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 identifies the verb 'Return' and the resource 'separate private contexts for all configured leagues,' which distinguishes it from siblings like discover_leagues. It implies a scope (all configured leagues) but doesn't specify what a 'context' includes.

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?

There is no explicit guidance on when to use this tool versus alternatives. Given the breadth of sibling tools (e.g., get_league_data, discover_leagues), the description lacks context on when this summary is appropriate or how it differs from those.

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