create_task

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

No annotations are provided, so the description must cover behavioral aspects. It discloses the date-only normalization behavior, which is useful. However, it lacks other important traits like authentication needs, whether the operation is idempotent, or what happens on error (e.g., invalid tasklist).

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 very concise: two sentences that first state the purpose and then add a crucial behavioral nuance. Every word earns its place, and the critical date handling is front-loaded after the purpose statement.

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 no output schema and 6 parameters, the description should mention return values (likely the created task) and potential errors. It omits these entirely. Given the complexity and sibling tools, the description is incomplete for an agent to fully understand the tool's usage and outcomes.

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 coverage is 100%, so the description's value is additive. It clarifies that 'due' should be date-only and provides standard format YYYY-MM-DD. This goes beyond the schema's description by explaining how the parameter is processed, which helps the agent choose correct values.

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. It distinguishes itself from sibling tools like list_tasks or delete_task through the name, but doesn't explicitly differentiate in the description. The added detail about date-only handling improves clarity.

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 specific guidance on due date format ('pass YYYY-MM-DD') and warns that time portions are discarded. However, it doesn't explain when to use this tool vs. alternatives (e.g., update_task for modifying tasks) or mention any prerequisites or exclusions.

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