Search players by name

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

Discloses return fields (name, position, etc.), pagination (max 25, page with start), and that it does not return stats. Consistent with readOnlyHint=true annotation; no contradictions.

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 main purpose, followed by importance, return fields, filters, and pagination in a compact paragraph. Could be slightly more structured, but no wasted words.

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?

Covers all essential aspects: purpose, input semantics, optional filters, pagination, and return fields. No output schema, but description explains what is returned adequately.

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 coverage, the baseline is 3, but the description adds context: explains that 'name' accepts full or partial, interprets 'status' enum values, and notes that 'leagueKey' defaults to configured league.

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 verb 'find' and resource 'players by name', and explains its role as a resolver to player keys for other tools, distinguishing it from siblings like list_players and rank_players.

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?

Explicitly says when to use: 'to turn a name the user typed into the player_key' needed by specific tools. Also implies when not to use by noting it returns no stats, and mentions optional filters without alternative guidance.

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