find_player

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

Describes search behavior (partial, case-insensitive), matching fields, and return content (IDs, team info). No annotations exist, so description carries the burden; it is transparent but could mention result limits or ordering.

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 highly efficient sentences that front-load the purpose and provide all necessary information with zero waste.

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?

Adequately covers purpose, parameters, and returns for a simple search tool. Could mention handling of multiple matches or default behavior, but sufficient for common use cases.

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 provides 100% coverage with a description that repeats the same information as the tool description (partial, case-insensitive). No additional meaning added beyond what schema already states.

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?

Specifically states 'search for players by name (partial, case-insensitive)' and distinguishes from sibling get_players by clarifying this resolves a name to an ID without downloading the full roster.

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 advises to 'use this to resolve a player name to an ID without downloading the full roster', implying when to use it over alternatives. Does not list explicit exclusions but provides clear context.

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