get_profile_photos

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds the behavioral detail that only metadata is returned, not the image itself, and explains the offset/max_id filtering semantics. This adds some value beyond annotations, but is not richly detailed.

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: one sentence for purpose, one for scope qualification, and a short bullet list for the two explained arguments. No filler, efficient structure.

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?

Given the 4-parameter schema, the description covers only offset and max_id, omitting chat and limit. The output schema exists, so return values are covered elsewhere, but the parameter gaps and lack of usage notes leave the agent partially informed.

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 0% description coverage, so the description must compensate. It explains offset and max_id with semantic meaning, but leaves chat and limit unexplained beyond their schema defaults. This is partial compensation, not full.

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 tool lists profile photos (metadata only) for users/groups/channels, using a specific verb 'list' and resource 'profile photos'. It also explicitly notes 'without downloading', which distinguishes it from the sibling tool download_profile_photo.

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 implies when to use this tool: when you need profile photo metadata without downloading the actual images. It does not explicitly name alternatives or provide 'when-not-to-use' guidance, but the 'без скачивания' clause clearly sets the boundary against downloading tools.

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