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 real behavioral context beyond that: the response source ('audience analytics'), that it preserves the requested date range, and an explicit failure-mode instruction to report unavailability rather than reporting zero audience.

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?

Three tight sentences, front-loaded with the trigger condition, then the parameter guidance, then the failure-mode caveat. Little waste; only the restated default slightly duplicates the schema.

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 an output schema present, return-value explanation is unnecessary, and the description covers the trigger, the parameter choice, and the degraded-source case. The only gap is the absence of sibling routing guidance against dynamoi_get_artist_analytics and dynamoi_get_playlist_analytics.

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%, so the description must carry parameter meaning. It restates the range enum values and the 30d default, which the schema already declares, and says the date range is preserved in the response — but adds no detail on artistId semantics or how the range affects aggregation/granularity.

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+resource ('audience analytics') and enumerates the exact dimensions delivered: country, service, paid/free tier, daily trend. It does not explicitly differentiate itself from the sibling dynamoi_get_artist_analytics, so an agent must infer the boundary between 'audience' and 'artist' analytics.

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 triggering condition ('use this when the user asks about an artist's streaming audience by country, service, paid/free tier, or daily trend') and specifies the range parameter choice and its default. It stops short of naming when not to use it or which sibling to prefer for adjacent questions.

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