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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuine operational context beyond that: one bounded request with no polling or auto-retry, metered/delayed access tied to the connected account, affiliate 27 excluded, and the warning that an empty result does not imply no coverage.

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 purpose is front-loaded, but the remainder reads as a run-on string of clauses joined by semicolons, mixing useful constraints with low-value disclaimers ('No wagers, account changes or guarantee of returns') and the unclear 'Product data or price calculation' fragment.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a one-required-parameter tool this is close to adequate, but the complete absence of parameter documentation and sibling differentiation leaves the agent short of what it needs to invoke confidently.

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 0% for two parameters (path.id and query.include), so the description must carry the burden. It only hints that IDs are canonical ('Use returned canonical IDs') and says nothing about the id format, the event ID requirement, or the meaning of the 'include' query option, leaving the parameters largely undocumented.

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?

States a specific verb and resource (get team totals for an event), which is clear enough to act on. However, it offers no differentiation from close siblings such as v1GetTotals, v2GetTeamStats, or v1GetEventByID, so the agent must guess how this tool's scope differs from those.

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?

There is no explicit when-to-use guidance and no alternatives named. The clause 'Read-only Product data or price calculation' gestures at a context but is too garbled to tell the agent which sibling to pick or when to prefer this over v1GetTotals.

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