Inspect and View Chat Photo Content

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful return context ('Returns image metadata and preview') but says nothing about permissions, rate limits, or whether save_path triggers a download — modest added value over the structured data.

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 sentences, front-loaded with the core action before routing the agent to the alternative. Every sentence earns its place; minor room for tightening but no waste.

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 read-only tool with no output schema, the description supplies the key return information (metadata plus preview) and a sibling routing hint. It is largely complete, though it could say more about what 'preview' contains or how save_path behaves.

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 description coverage is 100%, so the schema already explains all five parameters including account, chat_id, photo_id, save_path, and message_id. The description adds no additional parameter meaning, so the baseline 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+resource ('Inspect and view photo content from a chat') and adds the return scope ('image metadata and preview'). It distinguishes itself from get_photo_sheet, but does not address other plausible siblings like list_photos or get_media_info, leaving some ambiguity for an agent choosing among photo tools.

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?

Gives a clear trigger ('Use when analyzing an image in a conversation') and names one alternative with its condition ('For bulk photo galleries, use get_photo_sheet'). It lacks any when-not guidance beyond that single case, so it stops short of a full 5.

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