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

With no output schema, the note that REST returns the raw image while MCP returns base64 is genuinely useful and non-obvious behavioral context an agent cannot get elsewhere. The trailing 'Read-only' duplicates readOnlyHint=true and adds nothing, but the transport-dependent return format is a real contribution.

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?

Three short, front-loaded sentences with the resource stated first and the return-format caveat immediately after. Only the redundant 'Read-only' clause fails to earn its place.

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 two-parameter read, the description covers the resource and the return shape, which is the main unknown given no output schema. It omits any note on what happens when a chat has no picture (null, 404, empty base64) and leaves one parameter undocumented.

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 only 50% — chat_id is documented in the schema, account_id carries just a uuid format with no description. The description mentions no parameters at all, so it fails to compensate for the undocumented account_id. A bare cross-reference to list_messaging_chats would have closed the gap.

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 names a specific resource — the picture of a conversation or group — which an agent can distinguish from a generic image fetcher. It is a noun phrase rather than a verb+resource statement, and it never explicitly says it downloads/retrieves, but combined with the title the intent is 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?

There is no statement of when to use this versus alternatives; the sibling get_attendee_picture (person picture vs chat picture) is the obvious confusion point and is never addressed. The only guidance is implicit in 'conversation or group'.

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