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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing a safe read operation. The description adds behavioral context beyond this: instructs to show public URLs and avoid internal IDs in the final answer, and describes the desired fallback behavior for empty results. No contradiction with annotations.

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?

Four sentences, each earning its place: purpose, exclusion, output formatting rule, and empty-case fallback. Front-loaded with the primary action and no filler or repetition.

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?

The description covers purpose, when-not-to-use, output presentation, and fallback behavior, and an output schema exists. However, with 8 parameters and no parameter descriptions, the lack of explanation for filtering/pagination options leaves some gaps, though the core invocation is clear.

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 compensate, but it does not explain any of the 8 parameters beyond implying artistId via 'one artist'. The filter parameters (limit, query, cursor, format, claimStatus, renderState, publishState) are left completely unexplained, offering no added meaning over the raw schema.

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 opens with a specific verb ('list'), resource ('free Smart Links for one artist'), and enumerates returned fields ('release title, public URL, publish state, claim state, render state, and theme'). It explicitly distinguishes from the sibling tool `dynamoi_list_campaigns`, making purpose unambiguous.

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?

Provides direct when-to-use guidance ('Use this when the user wants to list free Smart Links for one artist'), an explicit exclusion ('Do not use this for paid campaign lists; use dynamoi_list_campaigns'), and alternative actions when results are empty (suggesting create tools). This is exemplary.

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