lol-summoner-search

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

The description adds valuable behavioral context beyond the annotations. While annotations indicate read-only and non-destructive operations, the description specifies that this is a search/retrieval tool that may fail if the summoner isn't found, and provides guidance on how to handle such failures (asking about region). This enhances the agent's understanding of real-world usage patterns.

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 efficiently structured in three sentences: purpose statement, mandatory usage rule, and error handling guidance. Each sentence serves a distinct function with minimal redundancy. The only minor improvement would be slightly more polished phrasing in the error handling sentence.

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 read-only lookup tool with comprehensive annotations and full parameter documentation, the description provides excellent contextual guidance about when and how to use it. The main gap is the lack of output schema, but the description compensates by indicating what information will be returned (rank, win rate, match history). The error handling guidance is particularly valuable for agent decision-making.

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?

With 100% schema description coverage, the input schema already fully documents all four parameters. The description doesn't add any parameter-specific information beyond what's in the schema, so it meets the baseline expectation but doesn't provide additional value regarding parameter usage or relationships.

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 states the specific action ('Retrieves information') and resource ('about a specific summoner'), with concrete examples of what information is retrieved ('rank, win rate, and recent match history'). It effectively distinguishes itself from siblings like 'lol-summoner-game-history' by focusing on summoner profile data rather than detailed match history.

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 provides explicit usage instructions: 'If a user mentions a specific summoner or wants to know about themselves, you *must* always call this function.' It also specifies an alternative action for failure cases: 'If you can't find the summoner, ask to the user which region do they play.' This gives clear when-to-use and fallback guidance.

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