Create task

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

Annotations already indicate non-read-only and non-destructive behavior. The description adds a meaningful behavioral detail: the due field renders as an all-day item on Google Calendar. It does not describe return values, but no output schema exists, and the core mutation semantics are already covered by 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?

Two concise sentences: the first states the core purpose, the second clarifies the due format and points to the bulk alternative. No wasted words; information is front-loaded.

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?

With 6 parameters but 100% schema coverage, the description doesn't need to repeat all parameter details. It covers the key single-vs-bulk distinction and the due behavior. It omits mention of return values or permissions, but these are not critical given the annotations and schema, making this adequately 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 description coverage is 100%, so the baseline is 3. The description repeats the due date format (already in the schema) and adds the calendar rendering note, which the schema also already states. No additional parameter semantics are provided beyond the schema.

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 tool's action ('Create one task') and specifies the resource (task). It explicitly distinguishes from the sibling tool create_tasks by noting it creates a single task, not several at once.

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 provides direct usage guidance: use this for one task, and explicitly names create_tasks as the alternative for multiple tasks. This is clear when-to-use and alternative guidance, satisfying the highest bar.

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