audience.segments.create

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

No annotations are provided, so the description carries the full behavioral burden. Beyond the 'pro-only' access note, it says nothing about permissions, side effects, idempotency, or what a successful create returns.

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?

It is a single short phrase with no wasted words, but the brevity reflects under-specification rather than efficient editing. Nothing is front-loaded beyond the bare verb+resource.

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 a nested undocumented payload, no annotations, and no output schema, the description is drastically incomplete. An agent cannot call this correctly from the given information.

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 single required parameter is a nested object with 0% schema description coverage, and the description adds no information about its structure or required fields. An agent must construct this payload completely blind.

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+resource ('create segment') within the Audience namespace, which lets an agent distinguish it from siblings like segments.list/get/update/delete. The 'Audience:' prefix is boilerplate but the core purpose is unambiguous.

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 only guidance is the '(pro-only)' gating constraint. There is no indication of when to create a segment versus using audience.upload.start or segment-related hf tools, nor any prerequisites for the payload.

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