Create a person

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds only the domain detail that faces can be attached; it says nothing about duplicate-name handling, permissions required, or what the call returns, which is a real gap for a non-idempotent create.

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?

Front-loaded with the verb+resource, followed by one useful sentence and a terse API reference. Slight redundancy between the title line and the 'Create a new person' sentence, but overall tight with no wasted prose.

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 five-parameter, zero-required, non-idempotent mutation with no output schema, the description leaves open what is created and returned and how duplicates are treated. Annotations cover the safety side and the schema covers the inputs, so the definition is minimally viable but not fully self-sufficient.

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 the schema already documents all five body fields, and the baseline for high coverage is 3. The description contributes no additional parameter meaning (formats, defaults, constraints like birthDate format or color syntax).

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 (Create) and resource (person) and adds the domain fact that a person can have multiple faces assigned, which helps distinguish it from immich_create_face and immich_get_person. It does not explicitly name which sibling to prefer over it, but the create semantics are unambiguous.

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?

No when-to-use guidance, prerequisites, or alternatives are given. The clause about faces implies a modeling role but does not tell the agent when to create a person versus using immich_merge_people, immich_search_person, or immich_update_person. The agent must infer usage entirely.

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