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

Goes well beyond the annotations: it discloses that authorization is checked against the caller's own edit permission, that 'Overdue' is server-derived, and most importantly that the tool is PROPOSED rather than executed — returning status='confirmation_required' with an action_id and plan_token until confirm_action is called. That two-phase protocol is essential behavior no annotation conveys.

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?

Front-loads the core action and allowed transitions, then adds the permission rule and the confirmation protocol as short labeled statements. No filler sentences; every clause carries operational information.

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?

There is no output schema, but the description compensates by describing the confirmation response shape (status, action_id, plan_token). The main residual gap is the unexplained optional deadline parameter on a status-setting tool, which an agent could plausibly misuse.

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%, and the description only illuminates the status parameter — listing the four allowed values and excluding 'Overdue'. The meaning and role of assignment_id, project_id, and especially the optional deadline parameter (is it a deadline update bundled with the status change?) are left entirely undocumented.

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 (set assignment status) and then enumerates the exact lifecycle transitions: New → Active → Completed, or aside to Postponed. The explicit note that 'Overdue' is derived rather than settable further pins down what the tool can and cannot do, making it unambiguous against sibling mutators like erp_update_assignment or erp_archive_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?

Clear context for use (moving a single assignment through its lifecycle) plus an explicit exclusionary rule ('Overdue' is not settable). It also routes the agent to the confirmation workflow via confirm_action. It stops short of naming a direct alternative for bulk or field-level edits, so a 4 rather than a 5.

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