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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the change affects the library-visible name rather than slide content, which is meaningful context. However, it doesn't say whether the existing title is overwritten, what happens to an existing subtitle when the subtitle parameter is omitted, or what permissions are needed for a mutation.

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 short sentence, front-loaded with the verb and resource, and the parenthetical qualifier earns its place by scoping which title is affected. Nothing is redundant or 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 simple three-parameter mutation with full schema coverage and no output schema, the description covers the core purpose. The gap is mutation semantics: whether subtitle omission clears the existing subtitle and whether the change is reversible or requires ownership rights. That leaves an agent guessing on a write operation.

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 title, subtitle, and document_id are already documented in the schema. The description echoes title and subtitle as a pair but adds no syntax, length, or null/omit semantics beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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 and resource: 'Sets the deck's title (and subtitle)'. The clause 'the one seen in the library' disambiguates it from slide-level titles, which is genuinely useful. It doesn't explicitly contrast with landing_set_title or ads_set_title, but the deck prefix plus 'deck's title' makes the target document type clear.

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: an agent infers this is the tool for renaming a presentation in the library. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. use landing_set_title for landing pages). Adequate but leaves routing to inference.

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