send_local_photo

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

With no annotations, the description carries the full behavioral burden and delivers almost nothing: no mention of what happens if chat_id is omitted, whether images are compressed, size limits, error behavior on invalid paths, or whether captions/buttons are rendered. 'Full-preview' is the only behavioral hint and it is vague.

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 short, front-loaded sentences with no waste; the bilingual duplication is a stylistic choice rather than padding. Nothing an agent reads is irrelevant.

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?

A five-parameter messaging tool with no annotations and zero schema coverage needs more than one sentence. An output schema exists, so return values need not be explained, but the missing parameter semantics and delivery behavior make the definition inadequate for correct invocation.

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 0% across five parameters, so the description must compensate, but it only implies photo_path ('local image file'). It says nothing about caption, parse_mode, chat_id, or the nested inline_buttons structure, leaving four of five parameters without any semantic guidance.

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 states a clear verb and resource: 'Send a local image file.' The phrase 'full-preview photo' distinguishes it from siblings such as send_local_document or send_local_video, which send the same local file in a different rendering. It does not explicitly name those siblings, but the resource type does the distinguishing work.

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?

There is no statement of when to choose this tool over send_local_document or send_media_album, no prerequisites (file path accessibility, permissions), and no exclusions. The agent must infer usage entirely from the resource noun.

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