add_slide

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

With no annotations present, the description carries the full burden, and it does disclose two useful behaviors: the layout fallback chain ('Title and Content' then 'Blank') and the append-when-index-omitted default. It says nothing about what happens on an out-of-range index, whether the operation is persisted immediately, or what the call returns, which are meaningful gaps for a mutation tool.

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 purpose sentence is front-loaded and the Args block is compact and scannable. Every line earns its place; only the raw docstring formatting slightly detracts from readability.

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 simple two-parameter tool with no output schema and no annotations, the definition covers both inputs and their default behavior adequately. The remaining gap is the implicit requirement of an active presentation and the absence of any return-value or error context.

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%, so the description must compensate, and it largely does: both parameters are explained with their defaults and the semantics of omission. It does not say what values layout_name accepts beyond the two defaults, which leaves an agent guessing at valid layout names.

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 opens with a specific verb and resource: 'Add a new slide to the current presentation.' That distinguishes it from delete_slide, move_slide, and set_slide_text. It does not explicitly differentiate itself from duplicate_slide, which is the closest sibling an agent could confuse it with, so it falls short of a 5.

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?

Usage is only implied by the tool's purpose; there is no explicit statement of when to choose this over duplicate_slide for copying an existing slide, nor any prerequisite (e.g., that a presentation must already be open). An agent can infer the use case, but the definition provides no routing guidance.

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