Keynote: list themes

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the list is machine-local ('on this Mac') and its values are the exact strings needed downstream. It does not discuss caching or refresh behavior, but the read-only annotation makes that low-stakes.

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?

Two sentences, no filler. The scoping constraint and the downstream tool names are front-loaded so the agent can act without reading further.

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 shape need not be described, and annotations carry the safety profile. The description supplies exactly the missing piece — why to call it and where its output goes — making the definition complete for a zero-parameter enumerator.

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?

Zero parameters, so the baseline is 4. The description still characterizes the semantic payload of the enumeration (theme names passable to set_theme), which goes slightly beyond a bare listing.

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 (list) and resource (themes available in Keynote on this Mac), and scopes it to local availability. An agent can distinguish it from sibling listers like iwork_list_templates and iwork_list_design_kits.

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 the downstream consumers ('Use before keynote_set_theme or keynote_build_deck') and states the purpose of calling it ('to get valid theme names'). This is a clear when-to-use directive with the alternatives identified.

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