add_task_notification

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

Annotations provide no behavioral hints (all false). The description adds that relativeMinutes requires a due date, which is a useful precondition. However, it does not disclose side effects (e.g., overriding existing notifications), authorization needs, or the outcome if both time fields are provided. It partially compensates for the lack of annotations.

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 extremely concise (two sentences, 32 words) and front-loads the purpose. Every sentence is essential with no filler or redundancy.

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 4-parameter tool without an output schema, the description covers the core functionality and parameter logic. It misses some context: no mention of the fallback between taskId and taskName (though schema covers it), no clarification on handling missing required inputs (e.g., if both taskId and taskName are omitted), and no error behavior. Adequate but not complete.

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 100%, so baseline is 3. The description adds value by explaining the difference between absoluteDate and relativeMinutes, reinforcing the sign convention for relativeMinutes. It clarifies usage beyond the schema descriptions, such as emphasizing the mutual exclusivity.

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 the action: 'Add a notification (reminder) to a task'. It specifies the resource and verb, and distinguishes itself from siblings like 'list_task_notifications' and 'remove_task_notification' by focusing on addition.

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 description guides parameter selection ('Use absoluteDate for a fixed time, or relativeMinutes for an offset'), but does not provide explicit when-to-use or when-not-to-use guidance relative to alternative tools (e.g., when to use this vs. editing a task directly). No exclusions or prerequisites are stated beyond the due date requirement.

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