Update case order in plan

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

No annotations are present, so the description must carry the burden of disclosing behavior. It only shows the method name and an example value; it does not state that this is a write operation, require any permissions, or explain the effect on plan/case ordering. This is insufficient for a mutation tool.

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 short but under-specified. It is a fragment rather than a proper explanatory sentence. It leaves out essential context, so brevity here is not effective conciseness but rather omission.

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?

While the tool is simple (3 required scalar params, no output schema), the description is incomplete for safe invocation. It does not articulate the operation's purpose, distinguish from sibling plan tools, or provide any behavioral context. The agent must rely on the title and schema, which is insufficient.

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 100%, with sortkey already described as 'Display order in the plan, e.g. 10, 20, 30'. The description repeats the sortkey example but adds no new parameter meaning. Given high schema coverage, the baseline of 3 applies.

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 is a code reference 'TestPlan.update_case_order: sortkey, e.g. 10, 20, 30.' which names the method and gives an example sortkey but does not explicitly explain the tool's purpose. The title 'Update case order in plan' is clearer, but the description itself lacks a verb+resource statement, making it vague for an agent.

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 compared to alternatives like kiwi_plan_add_case or kiwi_plan_remove_case. The description only provides a sortkey example and does not mention context, prerequisites, or exclusions.

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