create_task

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Create' and lists arguments without mentioning permissions, reversibility, side effects on related entities, or any other operational details beyond the write operation.

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 compact and well-structured: a single action sentence followed by a clean parameter list. Every line conveys useful information with no fluff or repetition, making it easy to scan.

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, no annotations, and an output schema present, the description adequately documents all parameter meanings and provides a clear action. However, it lacks usage guidance and any operational caveats, making it a minimum-viable description rather than a comprehensive one.

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 description provides an Args section that explains each parameter, such as 'related_contacts: Comma-separated contact IDs to associate' and 'due_date: Due date, e.g. YYYY-MM-DDTHH:MM:SS.' This adds meaningful format and semantic context that the schema lacks (0% coverage), fully compensating for the schema's silence.

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 states 'Create a task in Nimble CRM.' with a specific verb and resource, clearly identifying the tool's function. It distinguishes from sibling tools like create_contact or create_deal by naming 'task' as the target, though it lacks additional scope or distinguishing details.

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?

There is no guidance on when to use this tool versus alternatives, nor any exclusions or context about task-related operations. The description only states the action, leaving the agent to infer usage from the tool name.

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