change_assignment_status

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the required permissions ('fieldwork_write/admin_write') and the confirmation safeguard ('exact assignment confirmation'), which is useful. However, it does not reveal side effects, whether the change is reversible, what happens to the assignment, or what the response looks like.

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 brief and front-loads the main action, but it is under-specified rather than appropriately sized. For a mutation tool with five undocumented parameters, the terse two-sentence structure omits essential information, so efficiency comes at the cost of usefulness.

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 five parameters, no annotations, no output schema, and a mutating operation, this description is not complete enough. It fails to define allowed statuses, explain confirmation semantics, clarify comment/profile purposes, or describe expected behavior, leaving critical gaps for an agent invoking the tool.

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 compensate, but it only hints at confirm_assignment_id through 'exact assignment confirmation.' It does not explain valid status values, the role of comment, or what profile controls, leaving an agent unable to construct a correct call confidently.

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 states the action 'Change assignment status,' identifying the resource and verb, and is distinguishable from siblings like change_assignment_quantity and change_assignment_target_area. However, it never defines what 'status' values are supported, leaving the core purpose vague for an agent that must decide between this and archive/unarchive, which are also status-like mutations.

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?

There is no guidance on when to use this tool versus alternatives such as archive_assignment, unarchive_assignment, or assign_assignment. The only contextual hint is the permission requirement, which says nothing about the conditions that should trigger this tool rather than a sibling.

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