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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful behavioral note that the rip state is only meaningful while a rip is actively in progress, but says nothing about rate limits, freshness/polling cadence, or auth needs for live data.

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?

A single dense sentence with the resource front-loaded and the activity condition appended. Efficient, though the nested possessives ('show's current break's digital-instant-rip state') are slightly hard to parse.

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 described, and annotations cover the read-only nature. The remaining gap is the sole input parameter's meaning, which the description only gestures at, leaving the agent to guess what 'id' references.

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% for the single required 'id' parameter, so the description carries the burden. It implies 'id' identifies a Fanatics Live show, which adds some meaning, but it never states the format (numeric vs slug) or whether it is a show, break, or channel id.

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 names a specific resource — a Fanatics Live show's current break's digital-instant-rip state — and enumerates the payload (spot claim/rip progress, currently revealing item), so the agent knows it retrieves live rip state rather than generic show data. However, it never explicitly names the retrieval verb and does not differentiate itself from siblings like fanaticslive_show or fanaticslive_channel.

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 trailing clause 'when a rip is actively in progress' gives an implicit condition for meaningful results, hinting the state may be idle otherwise. But there is no explicit when-to-use/when-not guidance and no named alternative (e.g. fanaticslive_show) for the case when no rip is active, leaving routing to inference.

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