sendPhoto

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

With no annotations provided, the description carries the behavioral burden, and it does so usefully by disclosing the 10 MB size limit, total dimension limit, aspect ratio limit, and the success return type. It does not mention failure behavior or nuances about URL/file_id uploads, but the key constraints are clearly surfaced.

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 concise and well-structured: the main action comes first, followed by the success return and then the key constraints. Every sentence adds information without redundancy or filler.

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?

Despite having 17 parameters and no output schema, the schema fully documents every parameter, so the description only needs to add invocation-critical context. It adds the necessary size/dimension constraints and the return type, making the tool callable without leaving major gaps.

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 baseline is 3, but the description adds meaningful constraints on the photo parameter that are not present in the schema, such as maximum size and dimension limits. This goes beyond simply restating the schema documentation.

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 specific verb and resource ('Send photos') and includes the success return value, so an agent immediately knows what the tool does. It does not differentiate itself from sibling send tools such as sendMediaGroup or sendDocument, but the name and description are unambiguous enough for basic selection.

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 guidance on when to use this tool versus alternatives like sendMediaGroup, sendDocument, or sendPhoto variants. The description only restates the action and adds constraints, which does not help an agent choose between this and closely related siblings.

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