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

While annotations handle the safety profile (destructive/write), the description adds valuable behavioral context by explicitly stating the operation runs within 'Apple Reminders'. This clarifies the scope of the execution environment.

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 two sentences are highly efficient; the first defines the function, and the second routes the alternative, leaving zero wasted language.

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 specific, high-level nature of the operation, the description, combined with the platform focus and routing to MS To Do, provides all necessary context for an AI agent to correctly determine suitability and invoke the tool.

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?

With 100% schema description coverage, the description does not need to elaborate on the parameters. It successfully uses the space to provide guidance on usage and scope, which is the appropriate function at this coverage level.

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 immediately identifies the specific action ('Marks a reminder complete') and the precise target application ('Apple Reminders (Reminders.app)'). It is distinct from other potential completion tasks.

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?

It provides explicit usage guidelines by telling the agent exactly when NOT to use it: if the reminder is in Microsoft To Do, it must use `todo_complete_task` instead, preventing incorrect tool selection.

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