telegram-get-profile-photo

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's statement 'Download profile photo' is consistent. However, it does not add behavioral details beyond what annotations provide, such as error handling or rate limits. The description provides minimal extra transparency.

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—two short sentences that efficiently convey the tool's purpose and output options. No redundant words or sections.

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 download tool with clear annotations and full schema coverage, the description covers the core functionality adequately. It does not mention error cases (e.g., entity not found) or the format of the inline image, but given the tool's simplicity, it is reasonably complete.

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?

Each parameter is fully described in the schema (100% coverage). The description adds little beyond restating the purpose of 'savePath' (inline vs file). It does not clarify default behavior for 'size' or provide format details beyond what schema lists. Baseline 3 is appropriate as schema does the heavy lifting.

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 explicitly states the action ('Download profile photo'), the target ('Telegram user, group, or channel'), and the output options ('Returns inline image or saves to file'). This clearly distinguishes it from siblings like 'telegram-get-profile' (profile info) or 'telegram-set-profile-photo' (upload).

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 tool versus alternatives (e.g., 'telegram-get-profile' for other profile data). No prerequisites mentioned, such as being logged in or having access to the entity. The description lacks explicit context for an AI agent to decide when to invoke this tool.

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