get_bbl_player_profile

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

No annotations provided, but description discloses data scope (career aggregates with phase splits), league restriction, and slug format; lacks mention of permissions or rate limits but adequate for a read-only 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?

Three concise sentences each serve a distinct purpose: tool output, league/slug details, usage guidance. No redundant text.

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 single parameter and no output schema, description provides sufficient context for selection and invocation; could include output format but not critical for basic usage.

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 covers parameter, but description adds value by specifying kebab-case format with an example, aiding correct parameter construction beyond schema definition.

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?

Description specifies the tool retrieves a BBL player's career batting and bowling aggregates with phase splits, clearly distinguishing it from league-specific siblings like get_ipl_player_profile.

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 search_bbl_players when slug is unknown, and warns not to use for WBBL, providing clear when-to-use and when-not-to-use guidance.

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