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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds nothing beyond the name: no indication of what data a 'series detail' response contains, whether an ID or full URL is required, or any failure/redirect behavior. It does not contradict the annotations, but it contributes no behavioral context.

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?

It is short, but this is under-specification rather than conciseness. A single four-word fragment carries no usable instruction, so brevity here is a defect, not an economy.

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. But for a detail-fetch tool whose only two inputs are undocumented and ambiguous (url vs path), the description omits the minimum needed to invoke it correctly. Nothing an agent needs to call it successfully is present.

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 opaque parameters (url and path), and the description supplies no clarification about which to use, their format, or whether they are alternatives. The description fails to compensate for the undocumented schema, leaving the caller guessing.

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 phrase 'series detail' names a resource (Rotten Tomatoes series) and implies a single-item detail fetch, so the purpose is inferable. However, it does nothing to separate this from the numerous sibling detail tools (rottentomatoes_movie, rottentomatoes_season, rottentomatoes_episode), so an agent cannot confidently pick it without comparing schemas.

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, no prerequisite, and no mention of the sibling tools (movie/season/episode/search) that would be the obvious alternatives. The description is a bare label with no routing information.

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