move_slide

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

The description does not disclose any behavioral traits beyond the basic action of moving. It does not mention side effects, such as whether the slide is selected after moving, if the operation is reversible, or any permissions required. With no annotations present, the description carries the full burden but fails to provide sufficient detail.

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 that immediately conveys the core action. It is front-loaded and free of redundancy, though it could be slightly expanded to include more detail without becoming wordy.

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 simplicity of the tool (2 required integer parameters, no output schema, no nested objects), the description provides a sufficiently complete overview of the operation. However, it lacks information about edge cases, error handling, or the effect on the presentation state, which would improve completeness.

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% with both parameters having clear descriptions (1-based indices). The description adds no further meaning beyond restating 'from one position to another'. Baseline of 3 is appropriate as the schema already documents the parameters adequately.

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 'moves' and the resource 'slide', specifying a change in position within the frontmost presentation. It is distinct from sibling tools, which include actions like add, delete, duplicate, or navigate slides, but none other that reorder slides.

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, nor are there any preconditions, error conditions, or context for usage. The description lacks explicit when-to-use, when-not-to-use, or alternative tool mentions.

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