Get Brawl Stars player

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

With no annotations supplied, the description carries full responsibility for behavioral disclosure. It only states the output is 'Full stats', but does not mention API rate limits, authentication requirements, error handling for invalid tags, or whether the tool is read-only.

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 extremely concise—a single sentence of five words. While this meets minimal requirements for brevity, it sacrifices useful detail, especially for parameter semantics and usage guidelines.

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 absence of an output schema and any annotations, the description should elaborate on the return value structure or data fields. 'Full stats' is vague and insufficient for an agent to understand the response format or decide if the tool meets its needs.

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 sole parameter 'tag' has no description in the schema (0% coverage) and the tool description adds no additional context. It does not explain what constitutes a valid tag, where to find it, or the required format, making it ambiguous for an AI agent.

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 'Full stats for a player by tag' clearly states the tool retrieves comprehensive player statistics using a unique identifier. It effectively distinguishes the tool from siblings like 'bs_get_player_battlelog' (which focuses on battle logs) and club-related tools.

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 no guidance on when to use this tool versus alternatives such as 'bs_get_player_battlelog' or 'bs_get_club'. There are no mentions of prerequisites, recommended contexts, or situations where this tool should be avoided.

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