get_mlc_player_profile

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

Describes returned data (aggregates, breakdowns, identity bridge) but does not explicitly state read-only or idempotent behavior. With no annotations, slightly less transparent.

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 concise sentences: first outlines purpose and content, second explains parameter format and discovery method. No superfluous 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?

For a tool with one parameter and no output schema, description covers all aspects: what it returns, how to use it, and how to obtain the required slug. No gaps identified.

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?

Adds format (kebab-case) and example (f-du-plessis) for 'playerSlug', which is absent in the schema (0% coverage). Provides value 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 clearly states tool provides MLC player career profile with batting/bowling aggregates, per-season breakdown, and identity bridge. Distinct from siblings like get_mlc_team_profile and get_player_profile due to MLC specificity.

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 instructs to use search_mlc_players to discover slugs, providing clear guidance on when to use this tool vs. a sibling. Also specifies slug format with example.

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