sm_players

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

With no annotations, the description carries full behavioral burden. It only says 'Get football players' and 'Rich data with includes,' implying a read operation but omitting important behaviors like pagination, default mode, output shape, or how includes affect the response. This is minimal transparency for a 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?

The description is short and front-loaded with the action and resource. Both sentences are purposeful and free of filler, though the second sentence is terse and vague about what 'rich data' entails.

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?

The tool has 6 parameters, no output schema, and no annotations, but the description only scratches the surface. It doesn't clarify mode-specific requirements, pagination, or return data, so an agent cannot reliably construct a correct invocation without external knowledge.

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 description coverage is only 17% (only 'include' is described), and the description fails to compensate. It lists modes but omits the 'all' mode present in the schema, and gives no explanation of id, page, countryId, searchQuery, or which parameters apply to which mode.

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 clearly states 'Get football players' with a specific verb and resource, and adds mode variants. It distinguishes the tool from sibling tools focused on teams, standings, or odds, though it doesn't explicitly contrast with overlapping tools like sm_team_squads.

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 lists modes ('by_id', 'by_country', 'search') but provides no guidance on when to use each or how they differ. It also doesn't mention alternatives such as sm_team_squads for player squads, so an agent gets little help choosing between this and related tools.

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