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

The description frames the tool as a retrieval (a read), while the annotations declare readOnlyHint=false and idempotentHint=false, which assert the opposite — that the call is not a safe read and not repeatable. This is the inverse of the documented contradiction pattern and gives the agent conflicting signals about whether calling it can mutate state. The description also omits failure behavior for a bad presentation_id and any cost/size characteristics of summarizing a large deck.

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 front-loaded sentence with the returned fields enumerated immediately and zero filler. Nothing is redundant with the title or name, and no sentence could be removed without losing information.

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?

With no output schema, the description's enumeration of returned fields (titles, layouts, bullet counts, notes) usefully substitutes for one, which is a real strength. However, for a read-style tool whose annotations are actively misleading, the description should have stated its side-effect-free nature and error behavior rather than leaving the agent to trust contradictory hints.

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% — the single parameter presentation_id is already documented as the target .pptx identifier — so the schema carries the parameter burden. The description adds nothing further about identifier format, where the id comes from, or what happens with an unknown id. Baseline 3 applies when the schema is fully self-documenting.

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 pairs a specific verb ("Retrieve") with a specific resource ("a presentation") and enumerates the exact fields returned: slide titles, layouts, bullet counts, speaker notes. That is far more informative than a bare name restatement. It stops short of distinguishing itself from adjacent inspection tools (e.g. office-word-mcp__get_document_outline or excel_describe_sheets), so no sibling differentiation is offered.

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 explicit when-to-use statement, no prerequisites, and no exclusions — only an implied "call this to look at a presentation." Nothing tells the agent whether this should precede editing tools like add_slide or apply_professional_design, or whether it is the right tool versus describing slides another way.

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