unibet_kambi_live_stats

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

No annotations are provided, so the description must carry the full burden. It states the return format but does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or any side effects. The tool is likely safe but not explicitly confirmed.

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 very concise: one sentence for purpose and one line for return format. It is front-loaded with the primary action and contains no redundant information.

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 no annotations, no output schema, and 4 parameters with 0% schema coverage, the description is minimally complete. It explains the return structure but omits parameter details and usage context. Among many sibling tools, it lacks guidance to help an agent decide when to use this specific live stats tool.

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?

The input schema has 4 parameters with 0% description coverage. The description only mentions eventId implicitly via 'for one Kambi event', but does not explain lang, market, or channel_id. The description adds no meaningful semantics beyond the schema's field names.

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 it returns live in-event statistics (scores, match summary) for one Kambi event, using the required eventId parameter. The name and description distinguish it from sibling tools like unibet_kambi_call and unibet_kambi_odds_ladder, which serve different purposes.

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 implies usage for retrieving live stats for a specific event, but does not explicitly state when to use this tool versus alternatives. No guidelines on when not to use it or which sibling tools to consider instead.

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