telegram_send_photo

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

Description indicates a write operation consistent with readOnlyHint=false, and mentions return value. It adds context on photo source types but does not elaborate on side effects or permissions; annotations already cover non-destructive nature.

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?

Concise: one-line purpose, followed by bullet points on accepted sources and output. No redundant sentences, front-loaded with key action.

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?

Covers input and output sufficiently for a send tool; missing details like bot membership requirements or failure modes, but acceptable given annotations (openWorldHint) and output schema indication.

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 descriptions for sub-properties (chat_id, photo, etc.) exist but top-level param 'params' lacks description. The tool description compensates by summarizing required fields and noting 'caption/parse_mode' formatting, adding value over schema.

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 'Send a photo to a Telegram chat' and details accepted photo sources (local file, URL, file_id) and optional caption, clearly differentiating from sibling send_* 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?

No explicit guidance on when to use this tool versus alternatives like telegram_send_document or telegram_send_video; the description implies usage by name but lacks context on exclusions or prerequisites.

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