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

Annotations already declare destructiveHint=true, and the description adds the important behavioral detail that the existing slide is replaced. It also explains the append special case and vaguely notes a measurement return, but it does not clarify what 'the measurer found' means.

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 very short and front-loads the core action: writing and replacing a complete slide. The append special case follows immediately, and no sentence is wasted.

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 write tool with full schema coverage and destructive annotations, the description covers the core action and replacement behavior. However, with no output schema, the return value is only vaguely described as 'what the measurer found,' which leaves a small completeness gap.

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%, so the baseline is 3, but the description adds meaningful semantics for the slide parameter: slide = total+1 appends at the end rather than replacing an existing slide. The html, title, and derived parameters are otherwise left to their schema descriptions.

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 states a specific verb and resource: 'Writes a complete slide' and clarifies it 'replaces the one there.' That distinguishes it from a pure insertion or incremental edit, but it does not name the sibling tools such as deck_insert_slide or deck_edit_slide explicitly.

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 gives clear usage context for writing a complete slide and for appending with 'slide = total+1.' It does not explicitly state when to prefer deck_insert_slide or deck_edit_slide instead, so alternatives and exclusions are left implicit.

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