zuckerbot_list_custom_conversions

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

With no annotations, the description carries full behavioral disclosure and the author steps up: it says it is a pure read, states it never binds or consumes an ad-account slot, and explains the pagination cursor contract. This gives an agent enough information to reason about side effects and repeated calls.

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?

Three sentences and each one earns its place: what is returned, side-effect and pagination behavior, and when to use the tool. The most differentiating information (it never binds an ad-account slot) appears early.

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?

There is no output schema, so the description compensates by listing the returned fields and mentioning next_cursor for pagination. It also provides the routing use case and the read-only safety guarantee, making the tool well-specified for an agent to select and invoke it confidently.

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 documentation coverage is 100%, so the schema already explains after and business_id. The description reinforces the pagination usage of after but does not add substantial new parameter meaning beyond what the schema provides.

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?

Clearly states it lists custom conversions on the connected ad account and enumerates the exact fields returned (id, name, rule, source event, pixel, availability). The plural 'list' differentiates it from get_custom_conversion or create_custom_conversion without forcing an agent to infer from the name.

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?

Explicitly gives a concrete use case: find the custom conversion id a campaign spec's optimisation_event should reference. It also explains pagination behavior for truncated lists. However, it does not explicitly mention alternatives like get_custom_conversion from create_custom_conversion or what to do when you need a single specific conversion.

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