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

Annotations already cover readOnly/idempotent/openWorld/non-destructive, and the description adds real value beyond them: metered usage tied to the connected account, one bounded request with no polling or retry, affiliate 27 exclusion, and the warning not to infer coverage from an empty result.

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 key purpose is front-loaded, but the body is a dense run-on mixing operational boilerplate ('Read-only Product data or price calculation') with policy notes. It is functional but not tight.

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 no explanation, and the description covers access model, exclusions, and empty-result interpretation. The main gap is the missing v1/v2 differentiation for a single-parameter lookup 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?

Schema description coverage is reported at 0% at the top level and the description never mentions sportID or its accepted values. The nested schema does carry a common-value mapping, but the description contributes no parameter meaning of its own.

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 conferences for a sport'), which is clear on its own. However, it does not distinguish itself from the sibling v2GetConferencesBySport, so an agent cannot tell which version to pick from the description alone.

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 when-to-use guidance and no mention of the v1 vs v2 alternative despite v2GetConferencesBySport being a sibling. 'Use returned canonical IDs' is downstream consumption advice, not a selection condition.

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