list_audiences

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

The annotation readOnlyHint: true already signals a safe read operation. The description adds only the HTTP method GET, which restates the read-only nature without providing additional behavioral context such as pagination, scoping, or token requirements. It does not contradict the annotation but contributes no extra transparency.

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 short phrase plus endpoint, extremely concise and free of unnecessary words. It is front-loaded and perfectly sized for a minimal list operation.

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 simple list operation, the read-only annotation, and a complete output schema, the description is minimally adequate. However, it omits context about the scope of the list (e.g., all audiences vs. account-specific) and any special behavior. The output schema compensates for return format but the description remains thin.

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 coverage is 100%, with both parameters (ad_account_id and business_token) having clear descriptions of session fallback and override behavior. The description itself does not add any parameter semantics, so the baseline of 3 applies.

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 '오디언스 목록' (audience list) and the REST endpoint GET /targetings/audiences, making it clear this tool lists audiences. It is specific about the resource but does not explicitly distinguish itself from sibling list tools (e.g., list_campaigns) beyond naming the resource.

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 vs. alternatives. There is no mention of use cases, prerequisites, or exclusions relative to sibling list tools like list_ad_accounts or list_cohorts.

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