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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. However, for a renamed tool the single most important behavioral fact is missing: whether the tool still executes and returns data, or is deprecated and fails. Nothing is said about the response format, the rendered-PNG behavior, or lifecycle status.

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 short sentence with zero padding and the actionable instruction front-loaded. The terse 'Renamed:' fragment is slightly cryptic (renamed from what, and is this name still valid), but nothing is wasted.

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 simple 3-param read tool with 100% schema coverage, no output schema, and safety annotations, the description covers the migration path adequately. What it omits is the deprecation lifecycle detail an agent needs to decide whether invoking this tool is safe.

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% and the params (event_id, range, render) are fully documented in the schema, so baseline 3 applies. The description adds no parameter detail beyond the schema, though it does name the 'metric' value the replacement tool expects.

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 does; the purpose ('demand chart for an event') is only inferable from the name/title. It does usefully identify the tool as a renamed alias and points to its replacement, which helps an agent place it among siblings, but as a statement of purpose it is a redirect notice rather than a description.

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 names the alternative to use instead (get_event_chart) and the exact parameter that reproduces this tool's behavior (metric "demand"), which is precisely the routing information an agent needs. It stops short of stating whether calling this tool is still supported, errors out, or silently redirects.

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