search_bbl_players

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

No annotations, so description must bear burden. It mentions dataset size and seasons but does not disclose return format, error behavior, or idempotency. Implies read-only but not explicit.

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 sentences plus example and note. Front-loaded with key info. 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?

Given many sibling player search tools, description clearly delimits league scope. Provides pre-requisite context. Could mention pagination or output format but is sufficient for its purpose.

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 coverage is 100%. Description adds value for 'query' parameter with example and explanation of substring matching. For 'limit', it adds no new detail beyond schema.

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?

Clearly states tool finds BBL player slugs by substring match against full name or slug. Provides example and specifies league. Distinguishes from siblings by explicitly noting 'BBL only' and 'NOT for PSL/IPL/MLC 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 'Use before get_bbl_player_profile' and 'NOT for PSL/IPL/MLC players', giving clear context for when to use and when not to, with an alternative path.

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