get_bbl_team_profile

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

No annotations provided, so description carries burden. Lists return fields and valid slugs. Implicitly read-only (profile retrieval), but does not explicitly state lack of side effects or permissions needed. Sufficient for a simple data retrieval 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?

Two sentences plus a list. Front-loaded with purpose. Every word adds value. No redundancy.

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?

Despite no output schema, description fully defines return fields and acceptable inputs. Includes exclusion of non-BBL data. Adequate for an agent to invoke 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?

Schema coverage is 100% but description adds full list of valid team slugs, which is far more informative than schema examples. Also explains what returns (name, seasons, match count, canonical URL) providing context beyond parameter description.

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 it returns BBL franchise profile with specific fields (name, seasons, match count, URL). Distinguishes from sibling functions like get_team_profile (general) and other league-specific profiles by explicitly scoping to BBL and noting it does not return IPL/PSL data.

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?

Specifies it is for BBL franchises and explicitly excludes IPL/PSL. However, no direct comparison with other sibling functions like get_team_profile or advice on when to choose this over alternatives; still clear enough for an agent.

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