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

With no annotations present, the description carries the burden and does well: it declares the operation read-only, describes the returned fields, and discloses the important edge case that slides_count is 0 when no deck is uploaded. It does not cover auth/permission requirements or error behavior, which keeps it below a 5.

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 that leads with alias identity, then payload contents, then the edge case, then the routing preference, then the safety note. Every clause carries information; nothing is padded.

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 two-parameter read tool with no output schema, the description supplies return-field inventory, the empty-deck case, read-only status, and the alternative tool. Nothing an agent needs to select or call it correctly is missing.

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 id and include_images parameters are already fully documented in the schema. The description mentions no parameter behavior or defaults, providing no added semantic value beyond the structured fields — the baseline of 3 applies.

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?

Names the exact resource and verb ('returns the agent's current Slide Presenter deck') and immediately states it is an alias of get_presentation. Enumerates the payload fields (PDF name, slides, look, CTA, voice, channels, link), so an agent can distinguish it from get_presentation and every set_presentation_* mutator.

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?

Explicitly says 'Prefer get_presentation' and explains the only legitimate use case ('kept for older clients'), which is a clear when-to-use/when-not-to-use rule. The read-only note further confirms it is a safe lookup rather than a modification path.

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