zuckerbot_create_custom_conversion

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

With no annotations provided, the description must fully disclose behavior. It partially covers permissions and error returns but omits key details: side effects, idempotency, return value on success, or asynchronous behavior. This leaves agents uncertain about the tool's full impact.

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?

Two short sentences, no redundant words, and the most critical information (purpose, prerequisites, error handling, parameter list) is front-loaded. Highly concise and well-structured.

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 tool has 5 parameters with nested objects and no output schema. The description does not explain what the tool returns (e.g., conversion ID, status), nor does it clarify if the operation is synchronous. For a creation tool, this leaves significant gaps in the agent's understanding of the outcome.

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%, so the schema already documents all parameters. The description adds an example for the rule parameter but largely restates schema information. Baseline score of 3 is appropriate as the description provides minimal additional meaning beyond the schema.

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 explicitly states 'Create a custom conversion on the connected ad account', using a specific verb and resource. It clearly distinguishes from sibling tools like list_custom_conversions and other creation tools.

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 mentions prerequisite permissions and an error case (insufficient_permission). It lists required and optional parameters, providing some usage context. However, it does not explicitly state when to use this tool over alternatives, though the context of custom conversion creation is clear.

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