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

The description explicitly says "additive" (non-destructive), but the annotations declare destructiveHint: true. This is a direct contradiction, leaving the agent with contradictory signals about the tool's safety profile.

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 two sentences, front-loaded with the primary verb, and includes the GraphQL mutation path without unnecessary fluff. Every sentence carries useful content.

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?

For a simple create tool with complete schema coverage and no output schema, the description covers purpose, required/optional parameters, and the mutation endpoint. It lacks alternative disambiguation or return behavior, but those are not strictly necessary here.

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 schema already provides full descriptions for all 5 parameters (100% coverage). The description merely restates their roles without adding constraints, relationships, or syntax details beyond the schema.

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 uses the specific verb "Creates" with the resource "task in Healthie" and clarifies additive behavior. This distinguishes it from sibling tools like healthie_create_note and healthie_list_tasks.

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?

It states required content and optional parameters, giving clear context for invocation. However, it does not explicitly mention when to use this tool over alternatives like healthie_create_note, nor any exclusions.

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