Reorder Slides

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It clearly states that invocation will fail due to missing API support, giving the agent full transparency about the tool's non-functionality.

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?

A single sentence conveys the entire message with zero wasted words. It is front-loaded with the critical 'Not implementable' phrase, making it immediately actionable.

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 non-functional tool, the description is complete: it states impossibility, the reason, and implies the tool should not be invoked. No additional details about return values or behavior are necessary.

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?

The description provides no meaning for the two parameters (presentationId, orderedSlideIds). Schema description coverage is 0%, and the description does nothing to compensate, even though the tool's non-functional status makes parameter details less critical.

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 unequivocally states that the tool is not implementable, specifying the exact resource (Canva Connect API) and missing endpoint. This clearly distinguishes it from sibling tools like add_slide and update_slide_content, which are functional.

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?

It provides an explicit when-not guideline: the tool should never be used because no API endpoint exists. While it doesn't name alternatives, the exclusion is absolute and unambiguous, which is strong guidance.

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