download_profile_photo

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

The description adds valuable behavior beyond the annotations: explains two output modes (inline as base64/ImageContent vs. writing to file and returning a path), the size options (640x640 or 160x160), and the inline size limit (≤1 MB). No contradiction with the annotations (readOnlyHint=false is consistent with file writing).

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 description is extremely concise: a single purpose sentence followed by a short argument list. Every sentence adds necessary detail, with no filler or redundancy.

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 4-parameter tool with an output schema, the description covers the key behavioral aspects: output modes, file vs. inline, and size variants. It does not explain the chat parameter format or download_dir purpose in detail, but these are reasonably inferable. The output schema exists, so return values need not be detailed.

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?

The schema has zero description coverage, so the description must compensate. It does explain download_big and inline with specific meanings and sizes, but chat and download_dir are not described beyond their schema names. Partial compensation, with two of four parameters getting meaningful semantic detail.

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 clearly states the verb (download), resource (avatar/profile photo), and target (user/chat), and distinguishes it from sibling tools like get_profile_photos (which lists photos) and download_media (generic media download). The mention of 'to disk or inline (base64)' adds scope.

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?

The description explains parameters and output modes, but does not explicitly state when to use this tool versus alternatives like get_profile_photos or download_media. Usage is implied by the description of the tool's function, but no explicit when/when-not guidance is given.

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