reorder_slide

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

With no annotations provided, the description carries full burden for behavioral traits. It fails to disclose whether indices are zero-based or one-based, what happens to other slides (if positions shift), or any side effects. This is a critical gap for safe usage.

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 a single concise sentence, which is easy to parse. However, extreme brevity sacrifices necessary detail, so while efficient, it is not optimally informative.

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 only two parameters and an output schema exists, the description still fails to provide basic context such as index conventions, return value information, or error conditions. It is incomplete for a tool that could easily mislead if used without understanding index handling.

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 explain the meaning of 'slide_index' or 'new_index' beyond their names. There is no indication of constraints like range, required order, or exclusivity, so the description adds no value over the 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?

The description 'Move a slide to a new position' clearly states the action and resource, using a specific verb and noun that distinguishes it from deletion or addition verbs, though it does not explicitly differentiate from sibling tools like reorder_slide vs. delete_slide+add_slide.

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 such as delete_slide or add_slide, nor are there any prerequisites or context (e.g., only for existing presentations). The description lacks any explicit usage direction.

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