send_photo

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

No annotations provided, so description must carry full burden. It discloses sources and default chat, but omits critical behavioral details like size limits, file accessibility requirements, error handling, or return value structure for a 12-parameter tool.

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?

Two sentences with no redundancy. The first sentence provides the core purpose, and the second adds key usage details. Efficient and well-structured.

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 12 parameters and no output schema or annotations, the description is too brief. It does not cover important aspects like return values, failure modes, or constraints (e.g., file size). Incomplete for a complex tool.

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 coverage is 100%, so baseline is 3. Description adds value for 'photo' (URL/path) and 'chat_id' (default) beyond schema, but does not elaborate on the other 10 parameters. Meets minimal standard.

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 it sends a photo to a Telegram chat, with additional context about sources and default chat. However, it does not explicitly differentiate from sibling tools like send_document or send_video, though the name implies the medium.

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 provides guidance on when to use (sending a photo) and mentions default behavior, but lacks explicit when-not-to-use or alternative tool references (e.g., send_media_group for multiple photos).

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