slides_set_speaker_notes

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

With no annotations provided, the description carries the full burden. It explicitly discloses that the tool 'replaces any existing notes', which is a key side effect. It does not mention permissions or reversibility, but for a simple setter this is a significant and useful disclosure.

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?

The description is a single, short sentence that directly conveys the operation and the main behavioral caveat. Every word earns its place, and there is no unnecessary jargon or repetition.

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?

Given the simplicity of the tool and the presence of an output schema, the description adequately covers the core behavior. It lacks some contextual guidance about prerequisites or error scenarios, but for a straightforward setter it is mostly complete.

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?

The schema has 0% description coverage and the tool description does not explain the individual parameters. It only implies that notes_text is the speaker notes and slide_id/presentation_id identify the target, but no additional detail is provided to aid the agent in formatting or scoping the parameters.

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 clearly states the action ('Set') and the resource ('speaker notes for a slide'). It also distinguishes this from sibling tools like slides_set_text by specifically targeting speaker notes, making its purpose unambiguous.

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 when to use the tool (setting speaker notes) but does not explicitly discuss alternatives or exclusions. There is no mention of when to prefer this over other slides_* tools, but the narrow scope makes the usage fairly evident.

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