penpot_group_shapes

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

No annotations provided, so description bears full burden. Explains z-order behavior (inserted at topmost shape's position), that shapes keep absolute positions, and return value. Could mention optional groupId parameter but it's not critical.

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?

Four sentences, front-loaded with purpose, no fluff. Each sentence adds 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?

Describes constraints, return values, and reverse operation. No output schema exists, so return description is adequate. Could note if groupId is optional (parameter existence) but not required.

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 explains shapeIds must be siblings and that groupId is returned, but does not describe fileId, pageId, or name parameters individually. Adds partial meaning beyond 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?

Clearly states the tool groups sibling shapes, matching Penpot's Ctrl+G behavior. Distinguishes from penpot_ungroup_shapes by naming the reverse operation.

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 indicates when to use (group shapes) and when to use the reverse tool (ungroup). Mentions constraint that shapes must share the same parent. Does not exhaustively list alternatives but provides sufficient guidance.

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