Update plant main photo

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

No annotations provided, so description carries full burden. It discloses the option to move current photo to gallery, but does not clarify default behavior (e.g., whether the current main photo is replaced without backup) or any required permissions. The endpoint is given but adds no behavioral context.

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 succinct sentences: purpose, key usage, endpoint. No wasted words, front-loaded with the core action.

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?

Covers external URL use and optional gallery move, but lacks explanation for selecting an internal photo (e.g., from gallery) as main. No mention of return value or error conditions. Adequate but incomplete for all scenarios.

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 coverage is 100%, baseline 3. Description adds clarity: it explains the relationship between external and photo, and the purpose of move_to_gallery. This goes beyond the 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 verb 'update' and resource 'main preview photo' are clearly stated. The description distinguishes this tool from siblings like 'hortusfox_add_plant_gallery_photo' and 'hortusfox_update_plant' by specifying it updates the main photo, not adding to gallery or modifying plant details.

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 guidance on when to set external=true and optional move_to_gallery. It implies when to use external vs internal, but does not explicitly contrast with sibling tools for when not to use this tool.

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