Keynote: set presenter notes

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly covered. The description adds genuinely new behavior: notes REPLACE existing content, dry_run operates on a throwaway copy and runs every check, and 'Arabic-safe' signals text-handling guarantees. It doesn't cover permissions or whether Keynote must be running, so not 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?

Four short sentences, front-loaded with the action and the slide-indexing convention. The routing sentence and dry_run sentence each earn their place. Minor cost: 'Arabic-safe' is unexplained jargon that costs a clause without conveying actionable meaning.

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?

An output schema exists, so return values need not be explained, and the description covers the key decision points (existing slide, dry_run preview, build_deck alternative). It omits any prerequisite about the deck being open/an accessible file, which for a mutation tool with openWorldHint=false would be useful.

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% and the dry_run parameter already documents the copy/preview behavior, so the schema is doing the heavy lifting. The description's '1-based' and dry_run sentences largely restate schema content; 'Arabic-safe' adds a small note about encoding but no syntax detail for `notes`.

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+resource ('Set the presenter notes of slide number `slide`') and explicitly distinguishes itself from siblings: 'Use for speaker notes on an existing slide. For a new deck, put notes in keynote_build_deck's outline instead.' An agent can route between this and keynote_set_slide_text / keynote_build_deck without opening schemas.

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 names when to use it (existing slide, speaker notes) and when to use an alternative (new deck → keynote_build_deck outline). It also gives conditional guidance on dry_run ('before broad or risky edits'), covering both the when and the how.

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