marketo_clone_form

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

No annotations are provided, so the description must fully convey behavioral traits. It states that a new form is created, implying a non-destructive copy, but lacks details on permissions, rate limits, or side effects. The minimal description does not sufficiently cover behavioral aspects beyond the basic operation.

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?

The description is two sentences, directly stating the purpose and key action. It is concise with no extraneous information, and the verb 'Clone' is front-loaded for quick comprehension.

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?

Given the lack of output schema and annotations, the description provides the essential function but omits details on return values, error handling, or folder type nuances (e.g., Folder vs. Program). It is minimally complete for a straightforward clone operation but could be more robust.

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 input schema has 100% description coverage, so the baseline is 3. The description adds little beyond the schema, only mentioning that the form is created 'under the specified name and folder', which corresponds to parameters already documented. No extra semantic value is provided.

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 clearly states the verb 'Clone' and the resource 'existing Marketo form', specifying that it creates a new form with identical fields and settings under a given name and folder. This distinguishes it from sibling clone tools like marketo_clone_email or marketo_clone_landing_page.

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 implies when to use the tool (to clone a form) but does not explicitly compare it to alternatives or state when not to use it. Given the specific name and context, the usage is clear but lacks explicit guidance on exclusions or alternative tools.

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