List open Keynote documents without launching a stopped application, so you can inspect active presentations.
List open Keynote documents. Does not launch a stopped application.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and idempotency profile is fully covered by structured data. The description adds one genuinely non-obvious lifecycle fact (it will not start a stopped app), but says nothing about pagination, result limits, or behavior when no documents are open.
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 short sentences, zero filler, with the core purpose front-loaded and the behavioral caveat immediately after. Every sentence earns its place.
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 no-argument list tool with rich annotations but no output schema, the definition covers what it does and one important caveat. It is missing pagination guidance (why offset up to 100000 exists), what fields a listed document returns, and how an empty result should be interpreted — real gaps for an agent assembling a workflow.
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 description coverage is 0%, so the description carries no information about 'limit' or 'offset'. Their conventional names and explicit ranges/defaults in the schema make them largely self-explanatory, which justifies the baseline-leaning 3 rather than a lower score, but the description fails to state that these control pagination of the returned document list.
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 ('List open Keynote documents') and the 'open' qualifier scopes it meaningfully against siblings like apple_keynote_list_slides or apple_pages_list_documents. It does not explicitly name a sibling to contrast with, so an agent must infer the distinction, but the operation itself is 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 clause 'Does not launch a stopped application' implicitly tells the agent when this tool will not work and that apple_keynote_open may be needed first, which is useful implied guidance. However, no alternative tool is named and there is no explicit when-to-use / when-not-to-use statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.