distribute_elements

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to state whether this tool modifies element positions, requires a selection, or affects layout. No side effects, limitations, or operational details are disclosed.

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 extremely brief, but it is under-specified rather than impactful. It front-loads the core action, but fails to provide context that would be expected for a tool with two parameters and a direction enum.

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 tool has two parameters and appears to be a layout operation, the description is severely incomplete. There is no output schema, no annotations, and the description does not clarify what 'evenly' means spatially or how direction affects the operation.

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 0%, and the description does not mention either parameter ('elementIds' or 'direction'). It adds no meaning beyond what the schema already shows, leaving the agent to infer the purpose of each parameter.

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 'Distribute elements evenly' names a specific verb ('distribute') and resource ('elements'), but it is vague about what 'evenly' means (e.g., spacing, position, alignment). It does not distinguish from siblings like align_elements or group_elements, which could also involve arranging elements.

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?

There is no guidance on when to use this tool versus alternatives. No mention of prerequisites, selection requirements, or which distribution scenarios it handles. Sibling tools like align_elements suggest related functionality, but the description does not clarify boundaries.

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