search_leagues

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds search semantics and the output intent of discovering league IDs, but it does not disclose pagination behavior, ordering, or result limits. It does not contradict the 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?

Two short sentences with no wasted words. The core function is front-loaded, and the usage guidance is included in the second sentence. Every word earns its place.

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?

All 5 parameters are optional and fully documented in the schema, and the annotations cover the behavioral safety profile. The description explains the main purpose and return intent, discovering league IDs, which is sufficient for a simple search tool even without an output schema. Slightly more detail about pagination or response shape would make it fully complete.

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 100% parameter description coverage, so the baseline is 3. The description summarizes the filters as 'name, country or popularity', which roughly maps to search, country_id, and popular, but it adds no detail beyond what the schema already provides.

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 clear verb and resource: 'Find leagues' by name, country, or popularity. The added phrase 'Use this to discover league ids' gives an actionable purpose and distinguishes it from sibling tools that consume league IDs, though it does not explicitly contrast with search_countries or other alternatives.

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?

The description gives a clear invocation context: use it when you need to discover league IDs. This implies it is the right choice before calling tools like get_league_fixtures or get_standings, but it does not explicitly state when not to use it or name alternative tools.

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