update_person

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

With no annotations, the description carries the full burden. It mentions a side effect ('changes person metadata in Immich') and states that only provided fields are modified. However, it does not discuss permissions, rate limits, or reversibility of actions like hiding a person.

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 well-structured with a brief overview paragraph followed by an Args list. It is front-loaded with purpose and every sentence is useful. However, the Args section could be slightly more concise, but overall efficient.

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 the 7 parameters and lack of annotations, the description covers all parameters with context and explains the side effect. The return type is mentioned as 'JSON with the updated person object,' which is sufficient given the presence of an output schema (context signals indicate one exists). The description is fairly complete for a moderate-complexity 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?

The input schema has 0% description coverage, but the description provides detailed semantics for each of the 7 parameters in the Args section, including examples (e.g., '1990-05-15' for birth_date) and specific guidance (e.g., set name to name unnamed face clusters). This adds significant meaning beyond the schema.

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 clearly states 'Update a person's profile details' and lists specific use cases like naming unnamed faces, setting birth dates, hiding clutter faces, and changing the thumbnail. This distinguishes it from sibling tools such as get_person or search_people.

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 explicitly says 'Use this to name unnamed faces, set birth dates, hide clutter faces, or change the representative thumbnail.' This provides clear context for when to use the tool, though it does not mention when not to use it or suggest alternatives explicitly.

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