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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that results come from the Campaign Wizard and are filtered by audience type and targeting options, but does not add further behavioral context such as return shape, pagination behavior, or permission requirements.

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 front-loaded sentence with no redundant setup. It is appropriately sized for a read-only retrieval tool whose schema already carries detailed parameter documentation.

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?

The definition is adequate for a read-only tool with full schema coverage and annotations, but the audience-related sibling landscape is crowded. It lacks explicit differentiation from list_audiences and get_retargeting_audiences, and with no output schema it could do more to clarify what the returned matched audiences represent.

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 all five parameters are already documented in the schema. The description only broadly references audience type and targeting options, adding little beyond the structured parameter definitions.

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 a specific verb and resource: get matched audiences (custom audiences) from the Campaign Wizard. It also names the filtering basis, audience type and targeting options. It does not, however, distinguish this tool from nearby siblings such as list_audiences or get_retargeting_audiences.

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 implies filtering by audience type and targeting options, but gives no explicit when-to-use guidance. It does not name alternatives or explain when an agent should choose this instead of list_audiences, get_retargeting_audiences, or get_audience_details.

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