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

Annotations already declare this as a read-only, non-destructive operation, so the description is not required to restate safety. It adds the meaningful constraint that label-admin access is required, but otherwise does not elaborate on pagination behavior or result shape beyond what the schema and output schema already convey. 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?

The description is a single, well-structured sentence that leads with the operation and resource, states the scope options, and ends with the access requirement. Every phrase earns its place, and there is no redundant restatement of the tool name or schema.

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 read-only list operation, the description plus the fully described input schema and output schema cover the essential information an agent needs: purpose, scope options, access level, and expected output structure. The only minor gap is that 'label family' and 'Grow/ads' are not explicitly defined, but this is unlikely to block correct invocation given the sibling context and title.

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 100%, so the schema fully documents all six parameters including formats, defaults, and meaning. The description adds high-level context about artist and date scoping, but no parameter-level detail beyond what the schema already provides, so 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 names a specific action ('List'), a specific resource ('Grow/ads campaigns'), and a clear scope ('across a label family, optionally scoped to artists or date range'). This distinguishes it from sibling tools such as droptrack_list_ad_campaigns, which appears to be a broader/non-label listing, and droptrack_get_ad_campaign_details, which retrieves a single campaign.

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 provides a clear prerequisite ('Requires label-admin access') and implies the tool is for label-family campaign listing. However, it does not explicitly state when to prefer this over droptrack_list_ad_campaigns or other campaign-related siblings, nor does it describe exclusions such as non-label contexts.

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