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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description contributes only the hint that the response includes criteria and advanced configuration — useful given there is no output schema, but it does not explain depth, cost, or pagination behavior.

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?

One efficient sentence with the verb and content scope front-loaded and zero filler. It is well formed but so terse that the brevity edges into under-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?

For a read tool with no output schema, the description is the only place an agent could learn what 'deep' detail actually contains, and it offers just two vague nouns. It also leaves unresolved overlap with the sibling get_audience_details, which the agent cannot resolve elsewhere.

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% and the single parameter already documents the array type, minimum of 1, minItems, and a concrete example. The description's plural 'audiences' is consistent with the array but adds no syntax or format detail beyond the schema. Baseline 3.

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?

States a verb (Get) and resource (audience details) plus a vague content hint ('criteria and advanced configuration'), but never explains what makes this retrieval 'deep' versus the sibling get_audience_details or list_audiences. An agent cannot tell from the description which of these audience-reading tools to pick.

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?

No when-to-use guidance at all: no mention of when to pick this over get_audience_details, list_audiences, or get_retargeting_audiences, and no prerequisites or call-ordering notes. The agent must infer selection from the name alone.

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