set_home_locationSet a farm's default home premises, or clear it by passing a null location ID. Does not alter move events or treat the location as an origin.
Set the farm default home premises. Pass location_id null to clear it. This never changes move events and is never assumed as an origin.
| Name | Required | Description | Default |
|---|---|---|---|
| farm_id | No | ||
| location_id | No |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations establish this is a non-destructive write (readOnlyHint=false, destructiveHint=false). The description adds real value beyond that: it discloses the clearable state via null and the important scope constraint that it 'never changes move events' and 'is never assumed as an origin', preventing incorrect assumptions about side effects.
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?
Three tight sentences with zero filler. The core action is front-loaded and the clearing mechanism and scope constraints follow logically.
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 simple two-parameter mutation with annotations covering safety, the description covers purpose, clearing behavior, and scope constraints. Only farm_id semantics are unaddressed, a minor gap given its self-evident nature.
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 location_id semantics (null clears it) but says nothing about farm_id, leaving half the parameters undocumented beyond their type.
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 the farm default home premises'), clearly identifying the operation. It does not explicitly distinguish itself from related location tools like update_location or set_default_farm, so sibling differentiation is left implicit.
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?
The description provides an operational usage hint ('Pass location_id null to clear it') but offers no when-to-use guidance versus alternatives such as set_default_farm or update_location. Usage context is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.