penpot_batch

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

No annotations provided, so description carries full burden. It discloses that ops are applied in array order, each sees effects of prior ops, and create ops can set explicit IDs for later reference. Returns one result per op. This covers key behavioral traits beyond what schema alone provides.

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 front-loaded with the key benefit (single round trip) and efficiently covers operation types, ordering semantics, and inter-op references without wasted words. Every sentence adds distinct value.

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 complexity of batch operations and the absence of an output schema, the description adequately covers purpose, usage, operation details, and return format. It does not mention error handling or limits, but the core functionality is fully described.

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 0%, so description must compensate. It thoroughly explains the 'ops' parameter structure (four operation types, shape spec references penpot_add_shapes, update patch references penpot_update_shapes, etc.). However, it does not document 'fileId', 'pageId', or 'tokensPath' beyond their existence, leaving those parameters with only schema defaults/constraints.

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 states a specific verb+resource: 'Apply an ordered list of create/update/delete/reorder operations to a page as a single update-file change-set'. It clearly distinguishes from siblings like penpot_add_shapes and penpot_update_shapes by emphasizing batch execution and reduced round trips.

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 explains when to use (batching multiple shape operations) and contrasts with individual RPC calls ('instead of one RPC call per shape'), but does not explicitly define when not to use or list alternatives beyond referencing sibling specs.

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