Sets the x-index sorting value for a component in an ELN template to control its display order. Provide the component path and desired index to reorder elements precisely.
设置组件 x-index 排序值。
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| index | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says a sort value is set and does not reveal how the reorder behaves — whether it is a full reorder, how conflicts with other components' x-index are resolved, or whether the change is reversible.
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 text is extremely short, but this is under-specification rather than efficient conciseness. It front-loads nothing useful and every dimension suffers from the lack of detail.
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 two-parameter mutating operation with no annotations, no output schema, and zero schema descriptions, this description is inadequate. An agent cannot reliably determine what index values are valid, what path refers to, or what the outcome of a call will be.
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 adds nothing about either parameter. The meaning of 'path' (likely the component identifier) and 'index' (the sort position, and its bounds/format) is left entirely to inference, with no compensation from the description.
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 and resource: '设置组件 x-index 排序值' (set component x-index sort value). It is clear this reorders components, but it does not distinguish itself from similar siblings like move_component or reorder_formulas, which appear to overlap in function.
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?
No guidance is provided on when to use this tool versus alternatives. Given the presence of move_component and reorder_formulas, an agent receives no help deciding which one is appropriate for a given task.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.