discover_leagues

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only safety profile is established. The description adds useful context about user scoping and season format, but it does not disclose return shape, pagination, or any behavioral constraints beyond that.

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?

A single, front-loaded sentence with no filler. Every word earns its place, and it avoids repeating any schema field names or annotation details.

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?

For a simple read-only tool with one required parameter, the description provides the core operation and parameter format. The main gaps are the lack of output-shape hints and explicit routing relative to siblings, but these are minor given the tool's simplicity and the annotation coverage.

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 description coverage is 0%, so the description must carry the parameter-semantics burden. It adds meaningful meaning by specifying 'four-digit NFL season', which clarifies the expected format beyond the bare string type. An example value would strengthen it, but for one simple parameter this is solid compensation.

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 ('Find'), a resource ('configured user's leagues'), and a qualifier ('four-digit NFL season'). It is clear and not tautological, but it does not explicitly differentiate itself from close siblings like get_all_leagues_summary or get_league_data.

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 guidance on when to use this tool versus alternatives such as get_all_leagues_summary or get_league_data. The phrase 'configured user's' implies it applies to the authenticated user, but no explicit when-to-use, exclusions, or prerequisites are provided.

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