sportsbet_sport_competition

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

With no annotations, the description reveals the return structure and mentions optionality of top markets, but does not discuss read-only nature, side effects, or other behavioral aspects.

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 two sentences with a return type example, which is concise, but the code block could be better integrated.

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 6 parameters with 0% description, no output schema, and no sibling references, the description is insufficient for an AI agent to use the tool 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 0%, yet the description only hints at includeTopMarkets via 'optional top markets'. No explanation for numMarkets, displayType, eventFilter, includeAllEvents, or competitionId beyond its existence.

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 states it returns a competition page with matches, outrights, and optional top markets. It is clear about the resource and verb but does not differentiate from sibling tools like sportsbet_competition_matches or sportsbet_competition_outrights.

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?

No guidance on when to use this tool versus alternatives. No prerequisites or context provided.

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