searchPlayer

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

No annotations are provided, so the description carries the full burden. It mentions the tool returns 'matching profiles with basic stats,' which gives some behavioral context (e.g., it's a read operation with limited data). However, it lacks details on permissions, rate limits, error handling, or pagination, which are important for a search tool.

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 front-loaded and efficient: two sentences that directly state the action, input, and output without waste. Every sentence adds value, making it easy to parse quickly.

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?

Given the tool's moderate complexity (search with one parameter) and no annotations or output schema, the description is adequate but incomplete. It covers the basic purpose and output type but lacks behavioral details like result limits or error cases, which would help an agent use it correctly.

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 input schema has 100% description coverage, with the 'username' parameter documented as 'Username to search for.' The description adds minimal value by specifying 'username/battletag,' hinting at the format, but doesn't provide additional syntax or constraints beyond what the schema already covers.

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 tool's purpose: 'Find players by username/battletag' specifies the verb (find) and resource (players), and 'Returns matching profiles with basic stats for player lookup and comparison' explains the outcome. It distinguishes from siblings like getPlayerProfile (detailed profile) and getPlayerMatchHistory (match data), but doesn't explicitly name them.

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 implies usage for player lookup and comparison, suggesting it's for initial searches rather than detailed analysis. However, it doesn't explicitly state when to use this versus alternatives like getPlayerProfile or getPlayerMatchHistory, nor does it provide exclusions or prerequisites.

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