Habitica: create a task

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

Annotations already declare the mutation profile (readOnly=false, destructive=false, idempotent=false), so the description is not required to repeat them. However, the description adds no behavioral context beyond annotation coverage: it does not mention tag auto-creation, duplicate-handling, permission needs, or side effects, leaving most behavior to be inferred from the schema.

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?

Two short sentences, front-loaded with the action and task types, with no wasted words. It is concise and 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?

Although an output schema exists and the input schema is rich, this is a complex 12-parameter mutation tool with nested scheduling and tag creation behavior. The description does not provide enough context for an agent to understand usage conditions, side effects, or task-type-specific constraints beyond what the schema already says.

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 92%, so the schema already documents nearly all parameters in detail. The description adds only a minor clarification that tags are given by name, and even that slightly conflicts with the schema's 'Tag names (or ids)' wording; baseline 3 is appropriate when the schema carries parameter semantics.

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 a specific verb and resource: create one of four Habitica task types. It clearly distinguishes creation from scoring/updating/deleting siblings, but does not explicitly contrast with them or mention the task resource in a broader sense.

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?

No guidance is given about when to use this tool versus alternatives such as habitica_update_task, habitica_score_task, or habitica_delete_task. It also omits prerequisites or conditions for creating each task type.

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