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

Beyond the readOnlyhint and destructiveHinct, the description is narrates the five concrete eligibility checks, states that meeting all five does not guarantee approval, and clarifies that identity connections do not require advertising billing. It accurately confirms the read-only nature behavior and adds important context. No annotation contradiction.

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 most important use signal is front-loaded and each sentence contributes operational guidance. The list of five requirements is somewhat dense, but given the tool's complexity it is not wildly since long. It could be tightened slightly but still earns its length.

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 a tool that checks eligibility and status, the description fully covers when to use it, the five eligibility conditions, the approval caveat, and the fallback routing for missing face/meta or YouTube connections. With an output schema present, no essential behavior is unexplained.

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?

The schema description coverage is 0%, so the description was expected to compensate for the lone artistId parameter, but it never mentions that parameter. The property name and UUID format make the vague likely, but the description itself adds no direct semantic guidance about what identifier to pass or where it comes from.

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 begins with 'Use this when the user asks...' and enumerates three specific intents: eligibility, the five requirements, and existing application status. The resource (distribution application) and the action (get/check) are clear, so it cannot be confused with apply_for_distribution.

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 gives explicit triggers for using the tool and tells the agent what to do instead for missing identity: use another tool with purpose=distribution_identity or route the user to the Dynamo distribution application. This clearly separates it from the sibling connection and application tools.

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