Create VWO custom widgets in bulk

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

Annotations already indicate this is a write but non-destructive operation (readOnlyHint=false, destructiveHint=false). The description adds the rate limit constraint, which is behavioral context beyond annotations. No contradictions, but could mention failure behavior for partial batch failures.

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 concise sentences with no wasted words. Front-loaded with action and resource, then provides best practice guidance. Highly efficient.

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 bulk create tool with no output schema, the description covers purpose and rate limit but lacks details on error handling, idempotency, or response format. Given the complexity of the 'body' parameter and the lack of output schema, more context would be valuable but the description is minimally adequate.

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 description coverage is 100%, so the schema already documents all three parameters thoroughly. The tool description does not add additional parameter-level details beyond what is in the schema. Baseline of 3 is appropriate.

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 it creates several custom widgets in one request. The title includes 'in bulk', and the description distinguishes from repeated 'vwo_new_custom_widget' calls, making the purpose specific and well-defined.

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 advises to prefer this tool over repeated single creation calls due to VWO's 1 request per second rate limit. This provides clear when-to-use and when-not-to-use guidance, with a named alternative.

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