change_assignment_target_area

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose that the operation requires fieldwork_write/admin_write permissions and exact assignment confirmation, which are meaningful safety-related behaviors. However, it does not describe side effects, reversibility, validation behavior, or what happens upon success or failure.

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 filler. The core action comes first, followed by the most important safety and permission constraints. Every word earns its place.

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?

The tool is a mutation operation with no annotations, no output schema, and no parameter descriptions, yet the description provides only the action, a permission requirement, and a confirmation requirement. It omits valid target_area values, behavior for mismatched confirmation IDs, effect on existing assignment state, and return/error semantics. This is not enough for an agent to call it reliably in all cases.

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 for the four undocumented parameters. It adds some meaning to confirm_assignment_id via 'exact assignment confirmation' and implicitly clarifies target_area, but it leaves assignment_id and especially profile unexplained. This is only partial compensation for the complete lack of schema descriptions.

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 a specific verb and resource: 'Change assignment target area.' It is clear and accurately reflects the tool's operation, and the target-area focus helps differentiate it from sibling assignment tools. However, it does not explicitly differentiate from related tools such as change_assignment_quantity or change_assignment_status, so it misses the top score.

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 like change_assignment_quantity or change_assignment_status. The description only mentions permissions and exact assignment confirmation, which are prerequisites rather than usage context. An agent would have to infer when this tool is appropriate.

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