nexo_reminder_update

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

Describes that only non-empty fields are changed and requires a read token, indicating mutation behavior. However, no annotations are provided, so description carries full burden; lacks disclosure on side effects, reversibility, or return value.

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 concise, front-loaded sentences with no wasted words. First sentence states purpose and behavior; second gives critical prerequisite.

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?

Covers core update behavior and prerequisite but lacks return value information (no output schema) and does not fully differentiate from other reminder tools. Adequate but with 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 covers all 8 parameters (100% coverage). Description adds value by explaining the non-empty field behavior and the purpose of read_token via IMPORTANT instruction, beyond schema details.

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?

Clearly states 'Update fields of an existing reminder', distinguishing from create and delete. However, does not differentiate from nexo_reminder_note or nexo_reminder_complete, which are siblings.

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?

Explicitly instructs to call nexo_reminder_get first and pass its read_token, providing a clear prerequisite. Lacks guidance on when not to use (e.g., for completion or adding notes).

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