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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely useful semantics beyond that: the two-valued `kind` discriminator and the meaning of `no_storage` (org has not configured object storage), which tells the agent an empty result is a configuration state rather than a missing group. It does not mention URL expiry beyond "temporary".

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?

Short and front-loaded — the core action leads, followed by the return contract and the one non-obvious error code. The line breaks are awkward and the "same shape as a contact's picture" cross-reference assumes prior knowledge, but no sentence is wasted.

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 an output schema present, the description needn't enumerate return fields, and annotations plus a fully documented schema cover the rest. The only real gap is that it never says how long the temporary URL lasts or what to do on a not-found result, but nothing needed to call the tool correctly 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 coverage is 100% and both parameters are documented in detail in the schema, including the grp_/num_ prefixes and the wrong-inbox failure mode. The description adds nothing about parameters, 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?

States a specific verb and resource ("Get a group's picture") plus the fallback outcome ("or the reason there is none"), which distinguishes it from the sibling get_contact_profile_picture and from get_group. An agent knows exactly what this returns without opening the schema.

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 by the resource scope — this is the group-picture reader, and the contact sibling is referenced only obliquely via "Same shape as a contact's picture". There is no explicit statement of when to prefer get_group or get_contact_profile_picture instead, and no stated prerequisites.

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