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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds the useful temporal condition that the state is only meaningful during an active break, but does not describe behavior when no break is running or what the 'current state' contains. With annotations carrying the safety burden, a 3 is appropriate.

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?

Two tight sentences with the primary purpose front-loaded and the routing hint second. No wasted words.

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 restated, and the annotation covers the read-only nature. The description supplies the key temporal precondition. The only minor gap is what happens when the specified show has no active break.

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 100%, and the schema itself explains that 'id' is the Fanatics Live show id matching GET /fanaticslive/show/{id}. The description implies the id is a show id but adds no format, syntax, or sourcing detail beyond the schema. Baseline 3 when the schema does the work.

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 ('Fetch') and resource ('current digital instant-rip state for a Fanatics Live show'), and explicitly distinguishes itself from the closely related fanaticslive_show and fanaticslive_channel siblings. An agent can tell what this returns without opening the schema.

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?

Gives a clear precondition ('when a break is actively running') and routes to siblings ('Use fanaticslive_show for the show or fanaticslive_channel for its channel'). It lacks an explicit when-not statement (e.g., what to do if no break is active), so it falls just short of a 5.

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