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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description adds genuinely useful semantics beyond that: 'as they read now' conveys snapshot behavior, and 'higher rank is better and null means unranked, not zero' disambiguates a subtle data trait that annotations cannot express.

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?

Front-loads the core output ('One performer's numbers as they read now') before drilling into range semantics and routing. Slightly dense and the range sentence is a touch awkward, but nearly every sentence carries useful information.

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?

With no output schema, the description does the work of naming returned fields and the range semantics. For a read-only analytics tool with full schema coverage and covered annotations, this is essentially complete, though explicit 'when not to use' guidance is absent.

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 the baseline is 3. The description adds value over the schema by clarifying what 'range' actually governs — the performer's popularity rank over time, one row per date — which the schema only vaguely frames as a 'lookback window over snapshot_date'.

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 and resource ('get performer analytics') and enumerates exactly what it returns: popularity rank, average prices, listings, X activity, playoff odds, and prediction markets. It explicitly routes the agent away from get_event_analytics and names the sibling it replaces (get_performer_rank_chart), so it is distinguishable without opening a 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?

It names the alternative ('Use get_event_analytics for one event') and declares itself the replacement for get_performer_rank_chart, which gives clear routing context. However, it does not spell out an explicit when-not-to-use condition for this tool beyond the sibling pointer.

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