set_lemon_target_ip

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

No annotations are provided, so the description carries the full behavioral burden. 'Manually override' correctly implies a mutation, and the failure scenario adds useful context, but it says nothing about persistence, whether the override survives a restart, whether it affects active connections, or permission/auth requirements.

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 sentences, zero waste, and the primary action is front-loaded ahead of the conditional guidance. Every sentence 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?

For a two-parameter mutation tool with no output schema, the description covers purpose, trigger condition, and target resource adequately. It is slightly incomplete on post-set behavior and effects on the existing connection, which an agent might need to reason about consequences.

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 100%, so both 'ip' and 'port' are already fully documented in the schema including format example and default. The description adds no parameter-level detail beyond what the schema supplies, so baseline 3 applies.

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 ('override') plus resource ('target IP address of the iOS Lemon device'), with the 'Manually' qualifier signaling this bypasses automatic discovery. It is clearly distinguishable from its sibling get_lemon_target_ip, which reads rather than sets the value.

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?

Explicitly names the triggering conditions: use when mDNS/Bonjour discovery fails or when the device sits on a different network IP. This gives clear when-to-use guidance, though it never states when not to use it or that get_lemon_target_ip is the read counterpart.

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