send_photo

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

The description adds minimal behavioral context beyond annotations. It does not disclose potential side effects (e.g., message delivery), failure modes, or that the photo is fetched from the provided reference. With annotations offering little (readOnly=false, openWorld=true), the description carries the burden but fails to elaborate.

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 a single, well-structured sentence that directly states the action and the primary input. It is front-loaded and avoids wasted words.

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 tool with 15 parameters and no output schema, this description is under-specified. It does not provide an overview of typical use cases, optional features, or any context to help an agent correctly select and invoke the tool beyond the basic photo and chat_id.

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 only 47%, so the description must compensate for undocumented parameters. It only explains the 'photo' parameter, omitting context for chat_id, caption, reply_markup, parse_mode, and the many optional parameters. This is insufficient given the coverage gap.

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's function with a specific verb and resource: 'Send a photo.' It also specifies accepted input formats (file_id, HTTP URL, or absolute file path). This distinguishes it from sibling send_* tools like send_document or send_audio.

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 is provided about when to use send_photo versus alternatives (e.g., send_document for larger files, send_media_group for multiple photos). The description focuses only on how to pass the photo, not on the decision context.

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