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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable context beyond annotations by specifying what data is returned (metadata, per-slide summary, script presence, Q&A count, preview) and explicitly stating that slide images are NOT included, which prevents an agent from assuming it can retrieve image content. It does not cover pagination or error behavior, but for a read-only summary tool the disclosure is above average.

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 sentence delivering purpose, contents, and exclusions with zero waste and front-loaded information. Every clause earns its place.

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 one-parameter read-only tool with no output schema and annotations covering safety, the description is nearly complete: it tells the agent what the return contains and what it omits. The only minor gap is not clarifying what 'script preview' means (length, format), but an agent can invoke correctly without that detail.

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% and there is only one parameter (slug) required. The description does not name or explain the slug parameter, but with zero params documented in the schema the description still adds the key semantic of what the deck is by reference to its slug (the deck's summary). Given the single required parameter and its conventional name, the absence of explicit semantics is a minor gap; baseline for missing param info with low coverage would be lower, but the low complexity and conventional name justify a 4.

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?

States a specific verb (returns) and resource (deck metadata and per-slide summary), and enumerates exactly what is included: script presence per slide, Q&A document count, script preview. An agent can distinguish this from siblings like get_script (which returns script content) or list_decks (which lists decks) without opening any schema.

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?

The description implies the tool is for retrieving a summary view of a deck, and it explicitly notes that slide images are not included, which tells the agent when this tool is insufficient. However, it does not name alternatives (e.g., get_script for full script content) or state any preconditions (e.g., deck must exist, slug format). Usage context is implied but not explicit.

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