Create a local study task with estimated minutes. Set priority, notes, and timezone-aware due date to plan coursework.
Create a local study task with explicit estimated minutes. Estimated minutes must be 5..6000. Priority is 1..5; due_at needs timezone.
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | ||
| title | Yes | ||
| due_at | No | ||
| item_id | No | ||
| due_date | No | ||
| priority | No | ||
| estimate_minutes | Yes | Server validates: maximum=6000, minimum=5. |
Changes observed during successful MCP inspections.
v0.5.0Input schema / properties / due_at / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / due_at / oneOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / due_at / titleRemoved value: -"Due At"Input schema / properties / due_date / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / due_date / oneOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / due_date / titleRemoved value: -"Due Date"Input schema / properties / estimate_minutes / descriptionAdded value: +"Server validates: maximum=6000, minimum=5."Input schema / properties / estimate_minutes / maximumRemoved value: -6000Input schema / properties / estimate_minutes / minimumRemoved value: -5Input schema / properties / estimate_minutes / titleRemoved value: -"Estimate Minutes"Input schema / properties / item_id / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / item_id / oneOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / item_id / titleRemoved value: -"Item Id"Input schema / properties / notes / titleRemoved value: -"Notes"Input schema / properties / priority / titleRemoved value: -"Priority"Input schema / properties / title / titleRemoved value: -"Title"Input schema / titleRemoved value: -"study_task_createArguments"v0.4.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description usefully adds validation constraints (estimate 5..6000, priority 1..5, due_at timezone), but does not explain what 'local' scope means or how duplicates/conflicts are handled.
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?
Three short sentences, front-loaded with the purpose and then the validation rules. No filler, though the priority/due_at notes read slightly like a constraint dump rather than integrated guidance.
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 7 parameters, no output schema, and low schema coverage, the description leaves key semantics open: what item_id links to, how due_date differs from due_at, and whether notes are free-form. For a creation tool this is noticeably under-specified.
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 description coverage is only 14%, so the description must carry more weight; it does clarify estimate_minutes bounds, priority range, and the timezone requirement for due_at. However, four parameters (title, notes, item_id, due_date) and the due_at vs due_date distinction remain unexplained, leaving the compensation partial.
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?
States a specific verb and resource ('Create a local study task') and adds a distinguishing qualifier about explicit estimated minutes. It is clearly separable from study_task_update and study_tasks, though it does not name those siblings explicitly.
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 versus study_task_update, study_capture, or study_plan, and no prerequisites or preconditions are stated. The agent must infer usage purely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.