clio_create_task

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and domain, omitting any details about required permissions, return values, side effects, or prerequisites (e.g., matter must exist). This lack of transparency is similar to under-disclosed mutation tools.

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 a single, front-loaded sentence with no unnecessary words. It efficiently communicates the tool's purpose and scope, making it appropriately concise.

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 the tool has 4 parameters, no annotations, and no output schema, the description should provide more context about return values, requirements, or parameter usage. The description only covers the basic purpose, leaving significant gaps for a creation operation.

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 25% (only due_at has a description), yet the description does not compensate by explaining parameters. It merely hints that a matter is involved, which is already evident from the parameter name matter_id. The semantics of name, description, and due_at remain unexplained.

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 clearly identifies the action ('Create'), the resource ('task'), and the scope ('tied to a matter'). This distinguishes it from sibling tools like clio_create_matter or clio_create_contact, and there is no ambiguity about what this tool does.

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—this is for creating a task related to a matter—but it does not provide explicit when-to-use guidance or mention alternatives like clio_create_calendar_entry or clio_update_task. There is no exclusionary or comparative information.

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