list_themes

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

With no annotations, the description reveals a key behavioral trait: it attempts a direct query and falls back to a curated list. This adds useful transparency beyond a simple 'list' statement, though it does not cover other aspects like caching or error behavior.

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, well-structured sentence that conveys the purpose and a key behavioral detail without any wasted words. It is appropriately concise.

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 tool's simplicity (zero parameters, no output schema), the description provides sufficient context about what it does and how it behaves. It could be more complete by mentioning the return format, but for a basic list operation it is adequate.

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 tool has zero parameters, so the baseline is 4. No additional parameter semantics are needed; the description correctly implies no user input is required.

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 that the tool 'lists available Keynote themes' and specifies the behavior (direct query with fallback). This distinguishes it from sibling tools like list_templates and apply_theme by focusing specifically on themes and their retrieval strategy.

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 does not provide explicit guidance on when to use this tool versus alternatives. While it implies usage for viewing available themes, it lacks exclusion criteria or context for when to prefer list_themes over other related tools.

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