apple_reminders_create

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

The word 'local' adds a minor behavioral trait indicating the reminder is stored locally rather than synced. Annotations already indicate a write operation (readOnlyHint=false), so the description contributes little beyond this. No side effects, permissions, or return behavior are disclosed.

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, front-loaded sentence that wastes no words. However, it is so minimal that it borders on under-specification, though conciseness itself is strong.

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 has five parameters, no output schema, and no parameter descriptions, a one-sentence description is severely inadequate. It does not explain required fields, valid inputs, or expected behavior, leaving critical gaps.

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 coverage is 0% and the description provides no semantics for any of the five parameters (list, title, dueAt, notes, priority). The agent only has type/constraint information from the schema, which is insufficient for correct invocation.

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 a specific action ('Create') and resource ('Apple Reminder'), and the qualifier 'local' distinguishes it from other reminder operations like complete/delete/update. It effectively communicates the tool's primary purpose.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., apple_reminders_update, apple_reminders_complete). There are no prerequisites mentioned, such as needing an existing list or proper permissions.

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