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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is known. The description does add real behavioral context with '(the others move down)', clarifying that this is an insertion, not an overwrite. It does not say whether existing content can be clobbered, what is returned (e.g. new slide id) for follow-up edits, or any size/format constraints.

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?

One short sentence, front-loaded with the action and the scoping detail parenthetically. No filler, though it is arguably too terse given the sibling set.

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 five-parameter mutation tool with no output schema, the essentials for calling it are covered by the schema plus the shift-down note. What is missing is post-call context: whether the new slide's identifier/position is returned so the agent can immediately deck_edit_slide or deck_read_slide it, and how the required html field relates to the 'optional <style>' wording.

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%, so all five parameters, including position numbering and the derived-figures convention, are already documented in structured data. The description only restates the position behavior ('others move down'), adding no meaning beyond the schema, which is the baseline 3 case.

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 gives a clear verb and resource ('Inserts a new slide') and adds the positional semantics. It does not distinguish itself from close siblings such as deck_write_slide or deck_move_slide, so an agent must infer the boundary from names alone.

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 statement of when to use this rather than deck_write_slide (populate/edit a slide) or deck_move_slide (reorder). A single clause naming the create-vs-edit-vs-move distinction would close the gap; nothing is offered.

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