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

Annotations indicate readOnlyHint=false and destructiveHint=false, which is consistent with the mutating nature of reordering. The description adds valuable context: the handler rejects partial lists to prevent silent drops, and explains the z-index behavior. No additional behavioral traits (e.g., permissions, reversibility) are mentioned, but the core safety behavior is 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 only three sentences, all essential. It starts with the action, then explains the ordering, and ends with the critical usage constraint. No redundant or unnecessary content.

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?

The description covers the purpose, constraint, and prerequisite (get_clip). However, it does not mention the return value or any confirmation of success. Since there is no output schema, the agent would benefit from knowing what to expect after a successful reorder.

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 100%, so the schema already documents each parameter. The description adds the critical constraint that the handler rejects partial lists, which is not in the schema. This provides meaningful guidance beyond the parameter descriptions.

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 'Reorder' and the resource 'elements inside a clip', and explains the z-index ordering semantics. It distinguishes itself from sibling tools like add_elements and remove_elements by focusing exclusively on reordering existing 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?

The description explicitly instructs the agent to pass the full set of element IDs and warns that partial lists are rejected. It also directs the agent to get the current list via get_clip, providing a clear prerequisite. However, it does not explicitly state when not to use this tool or list alternative tools beyond get_clip.

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