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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is settled. The description adds valuable domain context: the response includes freshness and snapshot dates, and these are observed placements not attributed to a paid campaign. This is meaningful behavioral disclosure beyond annotations, though it omits error handling or rate-limit 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?

The description is three tight sentences, front-loaded with the usage trigger, followed by response content and an important caveat. Every sentence earns its place with no redundancy.

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 value documentation is not needed. The description still adds useful context about freshness/snapshot dates and non-attribution to campaigns. The only gap is that it doesn't elaborate on the artistId parameter, but given the single simple parameter, this is minor.

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?

There is only one parameter (artistId), and schema coverage is 0%, but the parameter name and UUID format in the schema make its meaning self-evident. The description doesn't discuss the parameter at all, but with a single obvious identifier, the baseline of 3 is appropriate.

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 states a clear verb+resource combination: it explains the tool returns an artist's tracked playlist placements, reach, and playlist movement. It's specific about what the tool does, though it doesn't explicitly distinguish itself from siblings like dynamoi_get_artist_analytics or dynamoi_get_audience_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?

It provides a clear when-to-use trigger: 'Use this when the user asks about an artist's tracked playlist placements, reach, or playlist movement.' This gives an agent a concrete condition for selecting this tool. It doesn't mention alternatives or exclusions, but the trigger is specific enough to route correctly in most cases.

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