List Ad Labels

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

Annotations already declare the tool as read-only, non-destructive, and idempotent. The description adds no behavioral traits beyond the basic listing action, such as pagination, rate limits, or error conditions. It does not contradict 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 short and front-loaded, but it omits the response_format parameter, making it incomplete. Every sentence is useful, but the missing parameter reduces its overall conciseness as a complete specification.

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?

Given the tool is simple and annotations cover safety, the description is minimally adequate but incomplete. It does not describe the return format or any additional context (e.g., label fields returned). The missing response_format parameter further detracts from completeness.

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 description only documents the ad_account_id parameter (as 'Ad account ID'), missing the response_format parameter which is present in the schema with an enum and default. Schema coverage is 50%, and the description fails to compensate by adding meaning or explaining the second parameter.

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 clearly states it lists ad labels for an ad account and explains what labels do. However, it does not differentiate this list tool from sibling list tools like list_ads or list_campaigns, which also list entities by account.

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 no guidance on when to use this tool versus alternatives. It lacks explicit context such as 'use when you need to view all labels' or 'not for searching by label name'. The only usage indicator is the tool's name itself.

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