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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is known. The description adds the "WRITE:" framing and the underlying endpoint (POST /tasks.json), which is modest added context. It says nothing about side effects an agent would care about—notably that notify_assignee can trigger an email to the assignee, or what permissions are required.

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 with the operation type front-loaded and no wasted prose. The trailing "Clio: POST /tasks.json" is mildly redundant with openWorldHint but is compact and harmless.

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 12-parameter mutation tool with no output schema, the description covers intent and the main optional axes but omits what the call returns (presumably the created task object) and says nothing about the four required fields or the notify side effect. Adequate given the fully documented schema, but not complete.

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 100% with enums documented, so the schema carries the parameter burden and a 3 is the baseline. The description adds light semantics beyond that—assignee may be a User or Contact and matter linkage is optional—but does not explain required fields or the interaction between assignee_type and assignee_id.

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+resource ("Create a task") plus the key scoping facts: assignee can be a firm user or contact, matter attachment is optional, due date and priority are supported. It is clearly distinguishable from siblings like clio_create_calendar_entry or clio_create_note by resource, though it never names an alternative 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?

No guidance on when to use this versus alternatives (e.g. clio_create_note for non-assigned work items) and no exclusions or preconditions. The only usage signal is the implicit "create" verb, leaving the agent to infer context.

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