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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the URL is temporary, the response is discriminated by `kind`, and `no_storage` is an organization setup gap rather than a contact-level fault — that last point materially changes how an agent should report the result.

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 core answer is front-loaded in the first sentence, and the following lines are a compact enumeration of result kinds. The prose is slightly padded by line-wrapping and the hedge 'may also simply have no picture', but nothing is wasteful.

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?

With a full output schema present, the description does not need to spell out return fields, and annotations cover safety. It supplies the interpretive context (temporary URL, no_storage vs. privacy-hidden) that the structured fields alone would not convey; only explicit routing versus get_contact is missing.

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%, with contact_id and number_alias both documented in the schema including the `ct_…`/`num_…` formats and the list_contacts/list_numbers sources. The description adds no parameter meaning on top of that, so the baseline of 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?

The description opens with a specific verb and resource — 'Get a contact's profile picture' — plus the notable framing that a negative result is also a valid answer. The resource noun 'contact' naturally separates it from the sibling get_group_picture, though no sibling is named explicitly.

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?

Usage is implied rather than stated: an agent learns that this tool returns either a picture or a reason, but not when to prefer it over get_contact (which likely also carries picture info) or what to do if the caller needs a fresh fetch. The `no_storage` explanation is interpretive guidance rather than a when-to-use rule.

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