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

Adds real behavioral context beyond annotations: two action modes, artist-wide scoping, no publish/unpublish, and sync vs background rendering. It does not detail destructive consequences despite destructiveHint=true, but annotations already flag that risk.

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?

Tight three sentences: trigger, action values, publishing boundary, and timing behavior. Every sentence earns its place with no repetition of schema content.

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?

For an 11-parameter, two-mode mutation tool with 0% schema coverage, this description is too thin. An agent cannot reliably know which IDs are required per action or what evidence fields like clientRequestId, expectedUpdatedAt, and userIntentSummary mean, even though an output schema exists.

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. It explains action's enum and the theme/pixel/description concepts, but leaves artistId, playLinkId, pixel IDs, clientRequestId, expectedUpdatedAt, userIntentSummary, and googleAdsConversionId unexplained and does not map parameters per action.

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 explicit use cases: changing a Smart Link's public description or updating artist-level theme/pixel settings. The update role is unambiguous against sibling create/get/list tools, and it explicitly rules out publish/unpublish behavior.

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?

Opens with 'Use this when...' and gives concrete triggers. It excluds publish/unpublish operations and clarifies artist-wide availability, though it does not name exact alternative tools for those cases.

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