Get a person

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that—no notes on error behavior for a missing/invalid id, auth requirements, or what the returned person object contains.

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?

Very short and front-loaded, with the operation and endpoint identifier clearly placed. There is mild redundancy in restating the title ('Get a person') and then 'Retrieve a person by id', but nothing is bloated.

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 read-only lookup with annotations covering safety, the description is adequate but thin. With no output schema, an agent gets no notion of what a person record contains or whether 404-style failures are expected, which are the main remaining unknowns.

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% for the single id parameter, so the baseline is 3. The description only echoes 'by id' and adds no format, source (e.g., where to obtain the person id), or validity detail beyond the schema's 'format: uuid'.

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 ('Retrieve a person by id'), so the operation is unambiguous. However, it does nothing to distinguish it from close siblings like immich_get_all_people, immich_search_person, or immich_get_person_statistics, which also act on 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?

No guidance on when to use this versus alternatives: there is no mention of search_person (lookup without an id) or get_all_people (listing). The 'by id' phrasing is the only hint, and that is already implied by the required id parameter.

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