Create an audience

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

Annotations only supply readOnlyHint=false, confirming this is a write operation, which the verb 'Create' already implies. The description adds nothing about required inputs, whether creation is synchronous, whether it needs a connected Meta ad account, or whether the new audience is immediately usable in campaigns.

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?

A single efficient sentence with the action front-loaded and no filler. It is appropriately sized for the sparse information it carries.

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 write tool with no output schema and an open-ended parameter object, the description should say what inputs are required and what the result is. Instead it only gives illustrative examples, so an agent cannot reliably construct a valid call.

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 declared schema has zero parameters, but additionalProperties=true means the tool actually accepts undocumented inputs. The description's examples ('website visitors', 'people similar to your customers') hint at an audience-type concept but never name the required fields (name, source, retention, lookalike ratio), leaving the real input contract opaque.

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 specific verb and resource ('Create an audience') plus the account scope ('in your Meta account') and two concrete examples of audience kinds. It is clear and distinguishing, though there are no audience-focused siblings to differentiate from.

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?

There is no when-to-use guidance, no prerequisites (e.g. ad account connection, minimum audience size), and no mention of alternatives such as reusing an existing audience. The examples describe audience types but do not tell the agent when this tool is the right call.

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