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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds no behavioral context of its own beyond the redirect – no return shape, no scope, no deprecation semantics beyond the word 'Renamed'. As a stub it is acceptable but contributes essentially nothing behavioral.

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 terse sentence with zero waste, and the redirect is front-loaded. It is appropriately sized for a deprecation stub, though it is arguably too thin to be self-sufficient.

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?

For a renamed/deprecated alias the key need is telling the agent where to go, which it does. However it leaves gaps: it does not say whether calling it still works, and it gives no hint about the returned data, which an agent must resolve by opening get_event_sellers.

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 100%, so event_id and hours are fully documented in the schema; baseline 3 applies. The description adds no meaning about either parameter – notably it does not explain how 'series' related to event_id or hours.

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 never states what the tool itself returns; it only announces a rename and points elsewhere. 'view "series"' hints at the resource (seller series data), but an agent learns the purpose only indirectly. It is better than a pure tautology because it names the replacement, yet it does not describe the tool's own function.

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?

It explicitly tells the agent not to use this tool and names the exact alternative plus the parameter value (get_event_sellers with view "series"). The when/when-not routing is unambiguous and requires no inference.

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