Create contact task

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

Annotations already indicate this is a non-read-only, non-idempotent operation. The description adds no behavioral context beyond the obvious create action; it does not mention return values, side effects, permissions, or what happens after creation.

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 short, focused sentences: one states the core action, the other flags the important date format. No redundant wording or filler.

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?

Adequate for a straightforward create operation, especially with schema and annotations present. However, with no output schema, the description should specify what the tool returns (e.g., created task object or ID) to fully support correct invocation.

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?

The schema documents 4 of 6 parameters. The description adds a concrete ISO 8601 example for dueDate, which is mildly helpful, but it does not clarify contactId, body, completed, or assignedTo beyond what the schema already provides.

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 'Create a task on a contact' gives a specific verb, action, and target resource. It clearly distinguishes this from the sibling task/update/get/delete operations and from other contact-related creation tools.

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 clearly implies use when creating a new task associated with a contact. It does not explicitly name alternatives or exclusion cases, but the sibling set makes the intended context reasonably clear.

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