Metis — Create Task

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

No annotations provided, so description carries full burden. It discloses key behaviors: default values for owner, recurrence auto-creation on completion, and subtask creation via parent_task_id. Does not discuss error conditions or side effects beyond 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?

Description is well-structured with a clear header and bulleted parameter list. It is reasonably concise, though some lines are slightly verbose. Every sentence adds value without 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?

Given 7 parameters (2 required) and an existing output schema, the description covers all parameters with meaningful explanations. It lacks discussion of edge cases or error handling, but for a create operation, the essential context is provided.

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 0%, meaning parameters have no descriptions in the schema itself. The description compensates fully by providing clear explanations for each parameter, including formats (e.g., YYYY-MM-DD for due_date), allowed values (e.g., recurrence options), and usage context (e.g., parent_task_id makes it a subtask).

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?

Description clearly states 'Create a new task in the SQLite database' with a specific verb and resource. It lists all parameters with explanations, distinguishing it from sibling tools like update_task and delete_task.

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 implies usage for creating tasks but does not explicitly state when to use this tool vs alternatives like update_task or delete_task. No guidance on when not to use it or context-specific recommendations.

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