keap_create_task

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

With no annotations, the description carries the burden. It reveals the API method (POST /tasks) and implies a write operation, but lacks details on side effects, permissions, error conditions, or response behavior. No additional context provided beyond the basic action.

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 well-structured and front-loaded. It opens with the core action, states the API, and then lists parameters in a readable format. Every sentence adds value; no fluff 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 tool with 8 parameters and no schema descriptions, the description covers all parameters and highlights required fields. It also notes the API endpoint and date format. The absence of return value explanations is mitigated by the existence of an output schema. It is sufficiently complete for an agent to invoke the tool correctly, though it could mention typical failure modes.

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 has 0% description coverage, so the description compensates by providing brief explanations for all 8 parameters. For example, it clarifies due_date format (ISO 8601) and lists allowed values for remind_time. However, some descriptions are generic (e.g., 'priority: Task priority') and could be more specific.

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 'Create a task' with a specific verb and resource, distinguishing it from sibling tools like keap_list_tasks (listing) and keap_create_note. It is concise and unambiguous.

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?

No explicit guidance on when to use this tool versus alternatives. It does mention required fields ('Must include at least a title and due date'), but does not explain when to choose this over other task-related operations or provide exclusions.

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