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

Annotations already declare that this is a non-read-only, non-idempotent, open-world write operation. The description adds useful behavioral context beyond annotations by disclosing that Lawcus may email or SMS assignees if reminders are set, and clarifies that this tool itself does not set reminders.

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 tight sentences, front-loaded with the write designation and core action. Every sentence contributes either purpose, optional relations, or important side-effect information, with no waste.

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 create mutation with annotations covering safety traits, the description supplies the critical side-effect caveat about notifications and clarifies optional associations. It still leaves some parameter semantics and return behavior unstated, but the schema and annotations carry the remaining structural burden.

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 60%, and the description adds meaning for matter_id and assignee_uuids by explaining that the task can optionally be attached to a matter and assigned to team members. However, it does not add information about the required name, due_date, or description parameters, leaving the partial schema coverage as the primary source.

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 a specific verb and resource ('create a task in Lawcus') and marks it as a write operation up front. It also distinguishes this from the sibling list/get tools by clearly stating the creation scope, including optional matter attachment and assignee assignment.

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 gives clear contextual guidance for when to use the tool: creating a task, optionally tied to a matter and assigned to team members. It does not explicitly state when not to use it or name any alternative tool, so it stops short of a 5.

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