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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to repeat safety traits. It adds non-obvious behavior: an empty result for a brand-new user should not be treated as a terminal 'no records found' answer, but instead should prompt a suggestion to create the first artist hub. This is useful context beyond the schema.

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 sentences, each with a distinct purpose: primary use case, exclusion, and empty-result fallback. No fluff and no repetition of schema or annotation information. The most important usage guidance is front-loaded.

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 the central search flow, the key exclusion, and a helpful empty-result edge case, and the output schema supplies return structure. However, it leaves gaps around optional parameters such as format, cursor, and includeArchived, and the 'release' mention does not map cleanly to any type enum value, so an agent may need extra inference for certain searches.

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 carries the burden of explaining the seven parameters, but it only loosely maps the search scenario to 'artist, release, campaign, or smart link'—and 'release' is not one of the type enum values. It does not explain query matching, cursor pagination, the difference between json and summary formats, artistId filtering, or includeArchived, leaving the agent to guess from names and enums.

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 specific exploratory use: searching when the user mentions an artist, release, campaign, or smart link but the exact record is unknown. It clearly distinguishes from analytics/billing flows by saying not to use it once the target record is known. However, it does not explicitly contrast search with the list_* sibling tools, so some ambiguity remains.

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?

The description explicitly gives the trigger condition, states when not to use the tool (analytics summaries or billing questions once the target is known), and provides a concrete alternative for the empty-result case on a brand-new user account by naming dynamoi_create_smart_links_from_spotify_artist. This is strong routing guidance with little left to inference.

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