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

Annotations only say this is a non-read-only, non-destructive local write, which is thin. The description adds the crucial fact that the tool is proposed-only, never executed directly, returns status='confirmation_required' with action_id and plan_token, and that the write occurs only after confirm_action — behavior an agent cannot get from any structured field.

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 plus a clearly labeled CONFIRMATION block; the proposal/confirmation semantics are front-loaded where an agent will see them before composing a call. No redundant restatement of the schema or annotations.

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 mutating 6-parameter tool with no output schema and no annotation depth, the definition covers the confirmation lifecycle and the trickiest parameter (assignee_id). Remaining gaps — deadline format, priority defaults, what the confirmed success result contains — are minor but real.

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 0%, so the description must carry parameter meaning. It explains assignee_id (employee id, omit to self-assign), implicitly project_id and title, and notes deadline is optional, but says nothing about the priority enum values, the free-text description field, or deadline format. Partial compensation only.

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 and resource ('Create an assignment (task) on a project') plus the optional dimensions (assignee, deadline), which is enough for an agent to recognize it as the creation counterpart to erp_update_assignment / erp_reassign_assignment. It stops short of explicitly naming those siblings, so the differentiation is inferable rather than stated.

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?

Gives concrete usage conditions: assignee is optional and omitting it self-assigns, and assignee ids must come from erp_list_employees. It also routes the agent to confirm_action for the actual write. No explicit when-not-to-use case is given relative to erp_update_assignment.

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