keap_create_task

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

With no annotations provided, the description must fully disclose behavioral traits. It only says 'Create a new task', implying mutation but no details on authentication requirements, side effects, default behaviors, or outcomes. For a create tool, this is insufficient transparency.

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 at 8 words, but this brevity under-specifies the tool's purpose and behavior given its 8 parameters. It does not earn its place because it adds minimal value beyond the tool name. Front-loading is not a concern as there is only one sentence.

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, no output schema, and no annotations, the description is woefully incomplete. It fails to mention return values, side effects, or any usage context. A create operation typically needs to indicate what the response contains (e.g., created task ID).

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 input schema has 100% description coverage, so each parameter already has basic meaning. The tool description adds no extra semantic information beyond the schema. Thus, baseline 3 is maintained; the description does not enhance parameter understanding.

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 new task in Keap' clearly states the action (create) and the resource (task). It is straightforward and avoids tautology by adding 'in Keap'. However, it does not differentiate from sibling create tools like 'keap_create_note' or 'keap_create_appointment', so it misses the top score.

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 no guidance on when to use this tool versus alternatives like 'keap_update_task' or 'keap_complete_task'. There is no mention of prerequisites, contexts, or when not to use it. It is a single sentence with no usage direction.

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