apple_pages_create

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

Annotations already declare the write/idempotency/safety profile, and the description adds traits they cannot express: the document starts unsaved, it may surface a UI window, and a name is returned for chaining. It still does not say what happens on failure or whether an invalid template errors, but the added context is real.

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?

Three short sentences, purpose front-loaded, no filler; each clause carries a distinct operational fact (unsaved state, possible window, chaining via returned name). Only the terse 'May show a window' leaves the consequence unstated.

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 mutation with no required parameters and no output schema, the description covers the essentials an agent needs: the object it produces, its transient unsaved state, the chaining handle, and the explicit save requirement. The undocumented templateName parameter is the main remaining hole.

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 only 50%: 'text' is documented in the schema, but 'templateName' has no description anywhere. The description mentions no parameter at all and therefore does not compensate for the coverage gap, leaving the agent to guess accepted template identifiers and default behavior.

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 ('Create an unsaved Pages document') with a distinguishing qualifier ('unsaved') that separates it from apple_pages_open, which works on existing files. It does not explicitly name a sibling, but an agent can still place it correctly among the create/open/save/close family.

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?

Gives concrete workflow guidance: the document is unsaved, the returned name must be used for follow-up operations, and a save must be requested explicitly. There is no explicit when-not condition, but the 'unsaved / save explicitly' framing effectively routes the agent to apple_pages_save.

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